An error occurred fetching the project authors.
  1. 20 Mar, 2008 1 commit
    • Randy Dunlap's avatar
      fs: fix kernel-doc notation warnings · a6b91919
      Randy Dunlap authored
      Fix kernel-doc notation warnings in fs/.
      
      Warning(mmotm-2008-0314-1449//fs/super.c:560): missing initial short description on line:
       *	mark_files_ro
      Warning(mmotm-2008-0314-1449//fs/locks.c:1277): missing initial short description on line:
       *	lease_get_mtime
      Warning(mmotm-2008-0314-1449//fs/locks.c:1277): missing initial short description on line:
       *	lease_get_mtime
      Warning(mmotm-2008-0314-1449//fs/namei.c:1368): missing initial short description on line:
       * lookup_one_len:  filesystem helper to lookup single pathname component
      Warning(mmotm-2008-0314-1449//fs/buffer.c:3221): missing initial short description on line:
       * bh_uptodate_or_lock: Test whether the buffer is uptodate
      Warning(mmotm-2008-0314-1449//fs/buffer.c:3240): missing initial short description on line:
       * bh_submit_read: Submit a locked buffer for reading
      Warning(mmotm-2008-0314-1449//fs/fs-writeback.c:30): missing initial short description on line:
       * writeback_acquire: attempt to get exclusive writeback access to a device
      Warning(mmotm-2008-0314-1449//fs/fs-writeback.c:47): missing initial short description on line:
       * writeback_in_progress: determine whether there is writeback in progress
      Warning(mmotm-2008-0314-1449//fs/fs-writeback.c:58): missing initial short description on line:
       * writeback_release: relinquish exclusive writeback access against a device.
      Warning(mmotm-2008-0314-1449//include/linux/jbd.h:351): contents before sections
      Warning(mmotm-2008-0314-1449//include/linux/jbd.h:561): contents before sections
      Warning(mmotm-2008-0314-1449//fs/jbd/transaction.c:1935): missing initial short description on line:
       * void journal_invalidatepage()
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      a6b91919
  2. 15 Feb, 2008 6 commits
  3. 08 Feb, 2008 1 commit
  4. 06 Feb, 2008 1 commit
    • Jan Kara's avatar
      inotify: send IN_ATTRIB events when link count changes · ece95912
      Jan Kara authored
      Currently, no notification event has been sent when inode's link count
      changed.  This is inconvenient for the application in some cases:
      
      Suppose you have the following directory structure
      
          foo/test
          bar/
      
      and you watch test.  If someone does "mv foo/test bar/", you get event
      IN_MOVE_SELF and you know something has happened with the file "test".
      However if someone does "ln foo/test bar/test" and "rm foo/test" you get no
      inotify event for the file "test" (only directories "foo" and "bar" receive
      events).
      
      Furthermore it could be argued that link count belongs to file's metadata and
      thus IN_ATTRIB should be sent when it changes.
      
      The following patch implements sending of IN_ATTRIB inotify events when link
      count of the inode changes, i.e., when a hardlink to the inode is created or
      when it is removed.  This event is sent in addition to all the events sent so
      far.  In particular, when a last link to a file is removed, IN_ATTRIB event is
      sent in addition to IN_DELETE_SELF event.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Acked-by: default avatarMorten Welinder <mwelinder@gmail.com>
      Cc: Robert Love <rlove@google.com>
      Cc: John McCutchan <ttb@tentacle.dhs.org>
      Cc: Steven French <sfrench@us.ibm.com>
      Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ece95912
  5. 12 Jan, 2008 1 commit
  6. 21 Oct, 2007 1 commit
  7. 18 Oct, 2007 1 commit
  8. 17 Oct, 2007 5 commits
  9. 16 Oct, 2007 1 commit
  10. 19 Jul, 2007 3 commits
  11. 17 Jul, 2007 1 commit
    • Satyam Sharma's avatar
      Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check · 3bd858ab
      Satyam Sharma authored
      Introduce is_owner_or_cap() macro in fs.h, and convert over relevant
      users to it. This is done because we want to avoid bugs in the future
      where we check for only effective fsuid of the current task against a
      file's owning uid, without simultaneously checking for CAP_FOWNER as
      well, thus violating its semantics.
      [ XFS uses special macros and structures, and in general looked ...
      untouchable, so we leave it alone -- but it has been looked over. ]
      
      The (current->fsuid != inode->i_uid) check in generic_permission() and
      exec_permission_lite() is left alone, because those operations are
      covered by CAP_DAC_OVERRIDE and CAP_DAC_READ_SEARCH. Similarly operations
      falling under the purview of CAP_CHOWN and CAP_LEASE are also left alone.
      Signed-off-by: default avatarSatyam Sharma <ssatyam@cse.iitk.ac.in>
      Cc: Al Viro <viro@ftp.linux.org.uk>
      Acked-by: default avatarSerge E. Hallyn <serge@hallyn.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      3bd858ab
  12. 11 May, 2007 1 commit
  13. 09 May, 2007 2 commits
  14. 08 May, 2007 2 commits
  15. 07 May, 2007 1 commit
  16. 27 Apr, 2007 1 commit
  17. 16 Feb, 2007 1 commit
  18. 12 Feb, 2007 1 commit
  19. 08 Dec, 2006 2 commits
  20. 07 Dec, 2006 2 commits
  21. 01 Oct, 2006 2 commits
  22. 29 Sep, 2006 1 commit
  23. 27 Sep, 2006 1 commit
    • Ian Kent's avatar
      [PATCH] autofs4 needs to force fail return revalidate · bcdc5e01
      Ian Kent authored
      For a long time now I have had a problem with not being able to return a
      lookup failure on an existsing directory.  In autofs this corresponds to a
      mount failure on a autofs managed mount entry that is browsable (and so the
      mount point directory exists).
      
      While this problem has been present for a long time I've avoided resolving
      it because it was not very visible.  But now that autofs v5 has "mount and
      expire on demand" of nested multiple mounts, such as is found when mounting
      an export list from a server, solving the problem cannot be avoided any
      longer.
      
      I've tried very hard to find a way to do this entirely within the autofs4
      module but have not been able to find a satisfactory way to achieve it.
      
      So, I need to propose a change to the VFS.
      Signed-off-by: default avatarIan Kent <raven@themaw.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      bcdc5e01
  24. 24 Sep, 2006 1 commit