1. 18 10月, 2007 1 次提交
    • L
      9p: attach-per-user · ba17674f
      Latchesar Ionkov 提交于
      The 9P2000 protocol requires the authentication and permission checks to be
      done in the file server. For that reason every user that accesses the file
      server tree has to authenticate and attach to the server separately.
      Multiple users can share the same connection to the server.
      
      Currently v9fs does a single attach and executes all I/O operations as a
      single user. This makes using v9fs in multiuser environment unsafe as it
      depends on the client doing the permission checking.
      
      This patch improves the 9P2000 support by allowing every user to attach
      separately. The patch defines three modes of access (new mount option
      'access'):
      
      - attach-per-user (access=user) (default mode for 9P2000.u)
       If a user tries to access a file served by v9fs for the first time, v9fs
       sends an attach command to the server (Tattach) specifying the user. If
       the attach succeeds, the user can access the v9fs tree.
       As there is no uname->uid (string->integer) mapping yet, this mode works
       only with the 9P2000.u dialect.
      
      - allow only one user to access the tree (access=<uid>)
       Only the user with uid can access the v9fs tree. Other users that attempt
       to access it will get EPERM error.
      
      - do all operations as a single user (access=any) (default for 9P2000)
       V9fs does a single attach and all operations are done as a single user.
       If this mode is selected, the v9fs behavior is identical with the current
       one.
      Signed-off-by: NLatchesar Ionkov <lucho@ionkov.net>
      Signed-off-by: NEric Van Hensbergen <ericvh@gmail.com>
      ba17674f
  2. 23 8月, 2007 1 次提交
  3. 15 7月, 2007 1 次提交
  4. 19 2月, 2007 1 次提交
    • E
      9p: implement optional loose read cache · e03abc0c
      Eric Van Hensbergen 提交于
      While cacheing is generally frowned upon in the 9p world, it has its
      place -- particularly in situations where the remote file system is
      exclusive and/or read-only.  The vacfs views of venti content addressable
      store are a real-world instance of such a situation.  To facilitate higher
      performance for these workloads (and eventually use the fscache patches),
      we have enabled a "loose" cache mode which does not attempt to maintain
      any form of consistency on the page-cache or dcache.  This results in over
      two orders of magnitude performance improvement for cacheable block reads
      in the Bonnie benchmark.  The more aggressive use of the dcache also seems
      to improve metadata operational performance.
      Signed-off-by: NEric Van Hensbergen <ericvh@gmail.com>
      e03abc0c
  5. 27 1月, 2007 1 次提交
  6. 04 12月, 2006 1 次提交
  7. 01 7月, 2006 1 次提交
  8. 26 3月, 2006 1 次提交
  9. 03 3月, 2006 2 次提交
  10. 09 1月, 2006 2 次提交
  11. 28 9月, 2005 1 次提交
    • L
      [PATCH] v9fs: fix races in fid allocation · 0b8dd177
      Latchesar Ionkov 提交于
      Fid management cleanup.  The patch attempts to fix the races in dentry's
      fid management.
      
      Dentries don't keep the opened fids anymore, they are moved to the file
      structs.  Ideally there should be no more than one fid with fidcreate equal
      to zero in the dentry's list of fids.
      
      v9fs_fid_create initializes the important fields (fid, fidcreated) before
      v9fs_fid is added to the list.  v9fs_fid_lookup returns only fids that are
      not created by v9fs_create.  v9fs_fid_get_created returns the fid created
      by the same process by v9fs_create (if any) and removes it from dentry's
      list
      Signed-off-by: NLatchesar Ionkov <lucho@ionkov.net>
      Cc: Eric Van Hensbergen <ericvh@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0b8dd177
  12. 10 9月, 2005 1 次提交