1. 17 Oct, 2006 1 commit
    • J. Bruce Fields's avatar
      [PATCH] knfsd: nfsd4: fix owner-override on open · dc730e17
      J. Bruce Fields authored
      
      
      If a client creates a file using an open which sets the mode to 000, or if a
      chmod changes permissions after a file is opened, then situations may arise
      where an NFS client knows that some IO is permitted (because a process holds
      the file open), but the NFS server does not (because it doesn't know about the
      open, and only sees that the IO conflicts with the current mode of the file).
      
      As a hack to solve this problem, NFS servers normally allow the owner to
      override permissions on IO.  The client can still enforce correct
      permissions-checking on open by performing an explicit access check.
      
      In NFSv4 the client can rely on the explicit on-the-wire open instead of an
      access check.
      
      Therefore we should not be allowing the owner to override permissions on an
      over-the-wire open!
      
      However, we should still allow the owner to override permissions in the case
      where the client is claiming an open that it already made either before a
      reboot, or while it was holding a delegation.
      
      Thanks to Jim Rees for reporting the bug.
      Signed-off-by: default avatarJ. Bruce Fields <bfields@citi.umich.edu>
      Signed-off-by: default avatarNeil Brown <neilb@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      dc730e17
  2. 04 Oct, 2006 2 commits
  3. 02 Oct, 2006 1 commit
  4. 10 Jul, 2006 1 commit
  5. 11 Apr, 2006 2 commits
  6. 07 Feb, 2006 1 commit
  7. 18 Jan, 2006 5 commits
  8. 13 Sep, 2005 1 commit
  9. 07 Jul, 2005 1 commit
  10. 24 Jun, 2005 3 commits
  11. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4