1. 23 Jun, 2006 1 commit
  2. 21 May, 2006 1 commit
  3. 11 Apr, 2006 1 commit
    • NeilBrown's avatar
      [PATCH] knfsd: nfsd4: fix acl xattr length return · b5872b0d
      NeilBrown authored
      We should be using the length from the second vfs_getxattr, in case it
      changed.  (Note: there's still a small race here; we could end up returning
      -ENOMEM if the length increased between the first and second call.  I don't
      know whether it's worth spending a lot of effort to fix that.)
      This makes XFS ACLs usable on NFS exports, which they currently aren't, since
      XFS appears to be returning a too-large value for vfs_getxattr() when it's
      passed a NULL buffer.  So there's probably an XFS bug here too, though since
      getxattr with a NULL buffer is usually used to decide how much memory to
      allocate, it may be a fairly harmless bug in most cases.
      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>
  4. 28 Mar, 2006 1 commit
  5. 19 Jan, 2006 4 commits
  6. 10 Jan, 2006 1 commit
  7. 09 Jan, 2006 1 commit
  8. 06 Jan, 2006 2 commits
    • Neil Brown's avatar
      [PATCH] knfsd: reduce stack consumption · 9f708e40
      Neil Brown authored
      A typical nfsd call trace is
       nfsd -> svc_process -> nfsd_dispatch -> nfsd3_proc_write ->
         nfsd_write ->nfsd_vfs_write -> vfs_writev
      These add up to over 300 bytes on the stack.
      Looking at each of these, I see that nfsd_write (which includes
       nfsd_vfs_write) contributes 0x8c to stack usage itself!!
      It turns out this is because it puts a 'struct iattr' on the stack so
      it can kill suid if needed.  The following patch saves about 50 bytes
      off the stack in this call path.
      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>
    • David Shaw's avatar
      [PATCH] knfsd: check error status from vfs_getattr and i_op->fsync · a334de28
      David Shaw authored
      Both vfs_getattr and i_op->fsync return error statuses which nfsd was
      largely ignoring.  This as noticed when exporting directories using fuse.
      This patch cleans up most of the offences, which involves moving the call
      to vfs_getattr out of the xdr encoding routines (where it is too late to
      report an error) into the main NFS procedure handling routines.
      There is still a called to vfs_gettattr (related to the ACL code) where the
      status is ignored, and called to nfsd_sync_dir don't check return status
      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>
  9. 07 Nov, 2005 1 commit
  10. 13 Jul, 2005 1 commit
    • Robert Love's avatar
      [PATCH] inotify · 0eeca283
      Robert Love authored
      inotify is intended to correct the deficiencies of dnotify, particularly
      its inability to scale and its terrible user interface:
              * dnotify requires the opening of one fd per each directory
                that you intend to watch. This quickly results in too many
                open files and pins removable media, preventing unmount.
              * dnotify is directory-based. You only learn about changes to
                directories. Sure, a change to a file in a directory affects
                the directory, but you are then forced to keep a cache of
                stat structures.
              * dnotify's interface to user-space is awful.  Signals?
      inotify provides a more usable, simple, powerful solution to file change
              * inotify's interface is a system call that returns a fd, not SIGIO.
      	  You get a single fd, which is select()-able.
              * inotify has an event that says "the filesystem that the item
                you were watching is on was unmounted."
              * inotify can watch directories or files.
      Inotify is currently used by Beagle (a desktop search infrastructure),
      Gamin (a FAM replacement), and other projects.
      See Documentation/filesystems/inotify.txt.
      Signed-off-by: default avatarRobert Love <rml@novell.com>
      Cc: John McCutchan <ttb@tentacle.dhs.org>
      Cc: Christoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  11. 08 Jul, 2005 1 commit
  12. 29 Jun, 2005 1 commit
  13. 23 Jun, 2005 1 commit
  14. 22 Jun, 2005 1 commit
  15. 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!