1. 09 1月, 2009 1 次提交
  2. 06 1月, 2009 1 次提交
    • C
      add a vfs_fsync helper · 4c728ef5
      Christoph Hellwig 提交于
      Fsync currently has a fdatawrite/fdatawait pair around the method call,
      and a mutex_lock/unlock of the inode mutex.  All callers of fsync have
      to duplicate this, but we have a few and most of them don't quite get
      it right.  This patch adds a new vfs_fsync that takes care of this.
      It's a little more complicated as usual as ->fsync might get a NULL file
      pointer and just a dentry from nfsd, but otherwise gets afile and we
      want to take the mapping and file operations from it when it is there.
      
      Notes on the fsync callers:
      
       - ecryptfs wasn't calling filemap_fdatawrite / filemap_fdatawait on the
         	lower file
       - coda wasn't calling filemap_fdatawrite / filemap_fdatawait on the host
      	file, and returning 0 when ->fsync was missing
       - shm wasn't calling either filemap_fdatawrite / filemap_fdatawait nor
         taking i_mutex.  Now given that shared memory doesn't have disk
         backing not doing anything in fsync seems fine and I left it out of
         the vfs_fsync conversion for now, but in that case we might just
         not pass it through to the lower file at all but just call the no-op
         simple_sync_file directly.
      
      [and now actually export vfs_fsync]
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      4c728ef5
  3. 20 11月, 2008 1 次提交
  4. 14 11月, 2008 2 次提交
  5. 27 10月, 2008 1 次提交
  6. 23 10月, 2008 1 次提交
    • M
      [PATCH] move executable checking into ->permission() · f696a365
      Miklos Szeredi 提交于
      For execute permission on a regular files we need to check if file has
      any execute bits at all, regardless of capabilites.
      
      This check is normally performed by generic_permission() but was also
      added to the case when the filesystem defines its own ->permission()
      method.  In the latter case the filesystem should be responsible for
      performing this check.
      
      Move the check from inode_permission() inside filesystems which are
      not calling generic_permission().
      
      Create a helper function execute_ok() that returns true if the inode
      is a directory or if any execute bits are present in i_mode.
      
      Also fix up the following code:
      
       - coda control file is never executable
       - sysctl files are never executable
       - hfs_permission seems broken on MAY_EXEC, remove
       - hfsplus_permission is eqivalent to generic_permission(), remove
      Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      f696a365
  7. 17 10月, 2008 1 次提交
  8. 27 7月, 2008 3 次提交
  9. 26 7月, 2008 1 次提交
    • A
      coda: remove CODA_FS_OLD_API · de0ca06a
      Adrian Bunk 提交于
      While fixing CONFIG_ leakages to the userspace kernel headers I ran into
      CODA_FS_OLD_API.
      
      After five years, are there still people using the old API left?
      Especially considering that you have to choose at compile time which API
      to support in the kernel (and distributions tend to offer the new API for
      some time).
      
      Jan: "The old API can definitely go.  Around the time the new
            interface went in there were some non-Coda userspace file system
            implementations that took a while longer to convert to the new API,
            but by now they all switched to the new interface or in some cases
            to a FUSE-based solution."
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Acked-by: NJan Harkes <jaharkes@cs.cmu.edu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      de0ca06a
  10. 22 7月, 2008 1 次提交
  11. 29 4月, 2008 2 次提交
  12. 15 2月, 2008 2 次提交
  13. 25 1月, 2008 1 次提交
  14. 20 10月, 2007 1 次提交
    • P
      pid namespaces: round up the API · a47afb0f
      Pavel Emelianov 提交于
      The set of functions process_session, task_session, process_group and
      task_pgrp is confusing, as the names can be mixed with each other when looking
      at the code for a long time.
      
      The proposals are to
      * equip the functions that return the integer with _nr suffix to
        represent that fact,
      * and to make all functions work with task (not process) by making
        the common prefix of the same name.
      
      For monotony the routines signal_session() and set_signal_session() are
      replaced with task_session_nr() and set_task_session(), especially since they
      are only used with the explicit task->signal dereference.
      Signed-off-by: NPavel Emelianov <xemul@openvz.org>
      Acked-by: NSerge E. Hallyn <serue@us.ibm.com>
      Cc: Kirill Korotaev <dev@openvz.org>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Cedric Le Goater <clg@fr.ibm.com>
      Cc: Herbert Poetzl <herbert@13thfloor.at>
      Cc: Sukadev Bhattiprolu <sukadev@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a47afb0f
  15. 17 10月, 2007 1 次提交
  16. 22 7月, 2007 1 次提交
    • J
      coda: remove CODA_STORE/CODA_RELEASE upcalls · d3fec424
      Jan Harkes 提交于
      This is an variation on the patch sent by Christoph Hellwig which kills
      file_count abuse by the Coda kernel module by moving the coda_flush
      functionality into coda_release.  However part of reason we were using the
      coda_flush callback was to allow Coda to pass errors that occur during
      writeback from the userspace cache manager back to close().
      
      As Al Viro explained on linux-fsdevel, it is impossible to guarantee that
      such errors can in fact be returned back to the caller.  There are many
      cases where the last reference to a file is not released by the close
      system call and it is also impossible to pick some close as a 'last-close'
      and delay it until all other references have been destroyed.
      
      The CODA_STORE/CODA_RELEASE upcall combination is clearly a broken design,
      and it is better to remove it completely.
      Signed-off-by: NJan Harkes <jaharkes@cs.cmu.edu>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Al Viro <viro@ftp.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d3fec424
  17. 20 7月, 2007 19 次提交