1. 29 6月, 2006 1 次提交
  2. 27 6月, 2006 1 次提交
  3. 23 6月, 2006 3 次提交
    • P
      [PATCH] read_mapping_page for address space · 090d2b18
      Pekka Enberg 提交于
      Add read_mapping_page() which is used for callers that pass
      mapping->a_ops->readpage as the filler for read_cache_page.  This removes
      some duplication from filesystem code.
      Signed-off-by: NPekka Enberg <penberg@cs.helsinki.fi>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      090d2b18
    • D
      [PATCH] VFS: Permit filesystem to perform statfs with a known root dentry · 726c3342
      David Howells 提交于
      Give the statfs superblock operation a dentry pointer rather than a superblock
      pointer.
      
      This complements the get_sb() patch.  That reduced the significance of
      sb->s_root, allowing NFS to place a fake root there.  However, NFS does
      require a dentry to use as a target for the statfs operation.  This permits
      the root in the vfsmount to be used instead.
      
      linux/mount.h has been added where necessary to make allyesconfig build
      successfully.
      
      Interest has also been expressed for use with the FUSE and XFS filesystems.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Acked-by: NAl Viro <viro@zeniv.linux.org.uk>
      Cc: Nathan Scott <nathans@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      726c3342
    • D
      [PATCH] VFS: Permit filesystem to override root dentry on mount · 454e2398
      David Howells 提交于
      Extend the get_sb() filesystem operation to take an extra argument that
      permits the VFS to pass in the target vfsmount that defines the mountpoint.
      
      The filesystem is then required to manually set the superblock and root dentry
      pointers.  For most filesystems, this should be done with simple_set_mnt()
      which will set the superblock pointer and then set the root dentry to the
      superblock's s_root (as per the old default behaviour).
      
      The get_sb() op now returns an integer as there's now no need to return the
      superblock pointer.
      
      This patch permits a superblock to be implicitly shared amongst several mount
      points, such as can be done with NFS to avoid potential inode aliasing.  In
      such a case, simple_set_mnt() would not be called, and instead the mnt_root
      and mnt_sb would be set directly.
      
      The patch also makes the following changes:
      
       (*) the get_sb_*() convenience functions in the core kernel now take a vfsmount
           pointer argument and return an integer, so most filesystems have to change
           very little.
      
       (*) If one of the convenience function is not used, then get_sb() should
           normally call simple_set_mnt() to instantiate the vfsmount. This will
           always return 0, and so can be tail-called from get_sb().
      
       (*) generic_shutdown_super() now calls shrink_dcache_sb() to clean up the
           dcache upon superblock destruction rather than shrink_dcache_anon().
      
           This is required because the superblock may now have multiple trees that
           aren't actually bound to s_root, but that still need to be cleaned up. The
           currently called functions assume that the whole tree is rooted at s_root,
           and that anonymous dentries are not the roots of trees which results in
           dentries being left unculled.
      
           However, with the way NFS superblock sharing are currently set to be
           implemented, these assumptions are violated: the root of the filesystem is
           simply a dummy dentry and inode (the real inode for '/' may well be
           inaccessible), and all the vfsmounts are rooted on anonymous[*] dentries
           with child trees.
      
           [*] Anonymous until discovered from another tree.
      
       (*) The documentation has been adjusted, including the additional bit of
           changing ext2_* into foo_* in the documentation.
      
      [akpm@osdl.org: convert ipath_fs, do other stuff]
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Acked-by: NAl Viro <viro@zeniv.linux.org.uk>
      Cc: Nathan Scott <nathans@sgi.com>
      Cc: Roland Dreier <rolandd@cisco.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      454e2398
  4. 24 5月, 2006 1 次提交
    • D
      JFS: Fix multiple errors in metapage_releasepage · b964638f
      Dave Kleikamp 提交于
      It looks like metapage_releasepage was making in invalid assumption that
      the releasepage method would not be called on a dirty page.  Instead of
      issuing a warning and releasing the metapage, it should return 0, indicating
      that the private data for the page cannot be released.
      
      I also realized that metapage_releasepage had the return code all wrong.  If
      it is successful in releasing the private data, it should return 1, otherwise
      it needs to return 0.
      
      Lastly, there is no need to call wait_on_page_writeback, since
      try_to_release_page will not call us with a page in writback state.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      b964638f
  5. 29 3月, 2006 1 次提交
  6. 27 3月, 2006 5 次提交
  7. 24 3月, 2006 3 次提交
    • P
      [PATCH] cpuset memory spread: slab cache format · fffb60f9
      Paul Jackson 提交于
      Rewrap the overly long source code lines resulting from the previous
      patch's addition of the slab cache flag SLAB_MEM_SPREAD.  This patch
      contains only formatting changes, and no function change.
      Signed-off-by: NPaul Jackson <pj@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fffb60f9
    • P
      [PATCH] cpuset memory spread: slab cache filesystems · 4b6a9316
      Paul Jackson 提交于
      Mark file system inode and similar slab caches subject to SLAB_MEM_SPREAD
      memory spreading.
      
      If a slab cache is marked SLAB_MEM_SPREAD, then anytime that a task that's
      in a cpuset with the 'memory_spread_slab' option enabled goes to allocate
      from such a slab cache, the allocations are spread evenly over all the
      memory nodes (task->mems_allowed) allowed to that task, instead of favoring
      allocation on the node local to the current cpu.
      
      The following inode and similar caches are marked SLAB_MEM_SPREAD:
      
          file                               cache
          ====                               =====
          fs/adfs/super.c                    adfs_inode_cache
          fs/affs/super.c                    affs_inode_cache
          fs/befs/linuxvfs.c                 befs_inode_cache
          fs/bfs/inode.c                     bfs_inode_cache
          fs/block_dev.c                     bdev_cache
          fs/cifs/cifsfs.c                   cifs_inode_cache
          fs/coda/inode.c                    coda_inode_cache
          fs/dquot.c                         dquot
          fs/efs/super.c                     efs_inode_cache
          fs/ext2/super.c                    ext2_inode_cache
          fs/ext2/xattr.c (fs/mbcache.c)     ext2_xattr
          fs/ext3/super.c                    ext3_inode_cache
          fs/ext3/xattr.c (fs/mbcache.c)     ext3_xattr
          fs/fat/cache.c                     fat_cache
          fs/fat/inode.c                     fat_inode_cache
          fs/freevxfs/vxfs_super.c           vxfs_inode
          fs/hpfs/super.c                    hpfs_inode_cache
          fs/isofs/inode.c                   isofs_inode_cache
          fs/jffs/inode-v23.c                jffs_fm
          fs/jffs2/super.c                   jffs2_i
          fs/jfs/super.c                     jfs_ip
          fs/minix/inode.c                   minix_inode_cache
          fs/ncpfs/inode.c                   ncp_inode_cache
          fs/nfs/direct.c                    nfs_direct_cache
          fs/nfs/inode.c                     nfs_inode_cache
          fs/ntfs/super.c                    ntfs_big_inode_cache_name
          fs/ntfs/super.c                    ntfs_inode_cache
          fs/ocfs2/dlm/dlmfs.c               dlmfs_inode_cache
          fs/ocfs2/super.c                   ocfs2_inode_cache
          fs/proc/inode.c                    proc_inode_cache
          fs/qnx4/inode.c                    qnx4_inode_cache
          fs/reiserfs/super.c                reiser_inode_cache
          fs/romfs/inode.c                   romfs_inode_cache
          fs/smbfs/inode.c                   smb_inode_cache
          fs/sysv/inode.c                    sysv_inode_cache
          fs/udf/super.c                     udf_inode_cache
          fs/ufs/super.c                     ufs_inode_cache
          net/socket.c                       sock_inode_cache
          net/sunrpc/rpc_pipe.c              rpc_inode_cache
      
      The choice of which slab caches to so mark was quite simple.  I marked
      those already marked SLAB_RECLAIM_ACCOUNT, except for fs/xfs, dentry_cache,
      inode_cache, and buffer_head, which were marked in a previous patch.  Even
      though SLAB_RECLAIM_ACCOUNT is for a different purpose, it marks the same
      potentially large file system i/o related slab caches as we need for memory
      spreading.
      
      Given that the rule now becomes "wherever you would have used a
      SLAB_RECLAIM_ACCOUNT slab cache flag before (usually the inode cache), use
      the SLAB_MEM_SPREAD flag too", this should be easy enough to maintain.
      Future file system writers will just copy one of the existing file system
      slab cache setups and tend to get it right without thinking.
      Signed-off-by: NPaul Jackson <pj@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4b6a9316
    • T
      [PATCH] fs: Use ARRAY_SIZE macro · e8c96f8c
      Tobias Klauser 提交于
      Use ARRAY_SIZE macro instead of sizeof(x)/sizeof(x[0]) and remove a
      duplicate of ARRAY_SIZE.  Some trailing whitespaces are also deleted.
      Signed-off-by: NTobias Klauser <tklauser@nuerscht.ch>
      Cc: David Howells <dhowells@redhat.com>
      Cc: Dave Kleikamp <shaggy@austin.ibm.com>
      Acked-by: NTrond Myklebust <trond.myklebust@fys.uio.no>
      Cc: Neil Brown <neilb@cse.unsw.edu.au>
      Cc: Chris Mason <mason@suse.com>
      Cc: Jeff Mahoney <jeffm@suse.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Nathan Scott <nathans@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e8c96f8c
  8. 15 3月, 2006 1 次提交
  9. 10 3月, 2006 1 次提交
    • D
      JFS: add uid, gid, and umask mount options · 69eb66d7
      Dave Kleikamp 提交于
      OS/2 doesn't initialize the uid, gid, or unix-style permission bits.  The
      uid, gid, & umask mount options perform pretty much like those for the fat
      file system, overriding what is stored on disk.  This is useful for users
      sharing the file system with OS/2.
      
      I implemented a little feature so that if you mask the execute bit, it
      will be re-enabled on directories when the appropriate read bit is unmasked.
      I didn't want to implement an fmask & dmask option.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      69eb66d7
  10. 09 3月, 2006 1 次提交
  11. 23 2月, 2006 2 次提交
  12. 16 2月, 2006 1 次提交
  13. 10 2月, 2006 1 次提交
  14. 09 2月, 2006 1 次提交
    • H
      JFS: ext2 inode attributes for jfs · fa3241d2
      Herbert Poetzl 提交于
      ext2 inode attributes with relevance for jfs:
      
      'a' 	EXT2_APPEND_FL       -> append only
      'i' 	EXT2_IMMUTABLE_FL    -> immutable file
      's' 	EXT2_SECRM_FL	     -> zero file
      'u' 	EXT2_UNRM_FL	     -> allow for unrm
      'A' 	EXT2_NOATIME_FL      -> no access time
      'D' 	EXT2_DIRSYNC_FL      -> dirsync
      'S' 	EXT2_SYNC_FL	     -> sync
      
      overview of jfs flags (partially for OS/2)
      
      value	   (OS/2)	Linux	ext2 attrs
      ------------------------------------------------
      0x00010000 IFJOURNAL	-
      0x00020000 ISPARSE  	used
      0x00040000 INLINEEA 	used
      0x00080000 -	    	-	JFS_NOATIME_FL
      
      0x00100000 -	    	-	JFS_DIRSYNC_FL
      0x00200000 -	    	-	JFS_SYNC_FL
      0x00400000 -	    	-	JFS_SECRM_FL
      0x00800000 ISWAPFILE	-	JFS_UNRM_FL
      
      0x01000000 -	    	-	JFS_APPEND_FL
      0x02000000 IREADONLY	-	JFS_IMMUTABLE_FL
      0x04000000 IHIDDEN  	-	-
      0x08000000 ISYSTEM  	-	-
      
      0x10000000 -	    	-
      0x20000000 IDIRECTORY	used
      0x40000000 IARCHIVE 	-
      0x80000000 INEWNAME 	-
      
      the implementation is straight forward, except
      for the fact that the attributes have to be mapped
      to match with the ext2 ones to avoid a separate
      tool for manipulating them (this could be avoided
      when using a separate flag field in the on-disk
      representation, but the overhead is minimal)
      
      a special jfs_ioctl is added to allow for the new
      JFS_IOC_GETFLAGS and JFS_IOC_SETFLAGS calls.
      
      a helper function jfs_set_inode_flags() to transfer
      the flags from the on-disk version to the inode
      
      minor changes to allow flag inheritance on inode
      creation, as well as a cleanup of the on-disk
      flags (including the new ones)
      
      beforementioned helper to map between ext2 and jfs
      versions of the new flags ...
      
      the JFS_SECRM_FL and JFS_UNRM_FL are not done yet
      and I'm not 100% sure they are worth the effort,
      the rest seems to work out of the box ...
      Signed-off-by: NHerbert Poetzl <herbert@13thfloor.at>
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      fa3241d2
  15. 25 1月, 2006 1 次提交
  16. 12 1月, 2006 1 次提交
  17. 11 1月, 2006 2 次提交
  18. 10 1月, 2006 1 次提交
  19. 09 1月, 2006 1 次提交
    • O
      [PATCH] Fix and add EXPORT_SYMBOL(filemap_write_and_wait) · 28fd1298
      OGAWA Hirofumi 提交于
      This patch add EXPORT_SYMBOL(filemap_write_and_wait) and use it.
      
      See mm/filemap.c:
      
      And changes the filemap_write_and_wait() and filemap_write_and_wait_range().
      
      Current filemap_write_and_wait() doesn't wait if filemap_fdatawrite()
      returns error.  However, even if filemap_fdatawrite() returned an
      error, it may have submitted the partially data pages to the device.
      (e.g. in the case of -ENOSPC)
      
      <quotation>
      Andrew Morton writes,
      
      If filemap_fdatawrite() returns an error, this might be due to some
      I/O problem: dead disk, unplugged cable, etc.  Given the generally
      crappy quality of the kernel's handling of such exceptions, there's a
      good chance that the filemap_fdatawait() will get stuck in D state
      forever.
      </quotation>
      
      So, this patch doesn't wait if filemap_fdatawrite() returns the -EIO.
      
      Trond, could you please review the nfs part?  Especially I'm not sure,
      nfs must use the "filemap_fdatawrite(inode->i_mapping) == 0", or not.
      Acked-by: NTrond Myklebust <trond.myklebust@fys.uio.no>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      28fd1298
  20. 29 11月, 2005 1 次提交
  21. 10 11月, 2005 1 次提交
  22. 01 11月, 2005 1 次提交
  23. 30 10月, 2005 1 次提交
    • H
      [PATCH] mm: split page table lock · 4c21e2f2
      Hugh Dickins 提交于
      Christoph Lameter demonstrated very poor scalability on the SGI 512-way, with
      a many-threaded application which concurrently initializes different parts of
      a large anonymous area.
      
      This patch corrects that, by using a separate spinlock per page table page, to
      guard the page table entries in that page, instead of using the mm's single
      page_table_lock.  (But even then, page_table_lock is still used to guard page
      table allocation, and anon_vma allocation.)
      
      In this implementation, the spinlock is tucked inside the struct page of the
      page table page: with a BUILD_BUG_ON in case it overflows - which it would in
      the case of 32-bit PA-RISC with spinlock debugging enabled.
      
      Splitting the lock is not quite for free: another cacheline access.  Ideally,
      I suppose we would use split ptlock only for multi-threaded processes on
      multi-cpu machines; but deciding that dynamically would have its own costs.
      So for now enable it by config, at some number of cpus - since the Kconfig
      language doesn't support inequalities, let preprocessor compare that with
      NR_CPUS.  But I don't think it's worth being user-configurable: for good
      testing of both split and unsplit configs, split now at 4 cpus, and perhaps
      change that to 8 later.
      
      There is a benefit even for singly threaded processes: kswapd can be attacking
      one part of the mm while another part is busy faulting.
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4c21e2f2
  24. 29 10月, 2005 1 次提交
  25. 28 10月, 2005 1 次提交
    • A
      [PATCH] gfp_t: fs/* · 27496a8c
      Al Viro 提交于
       - ->releasepage() annotated (s/int/gfp_t), instances updated
       - missing gfp_t in fs/* added
       - fixed misannotation from the original sweep caught by bitwise checks:
         XFS used __nocast both for gfp_t and for flags used by XFS allocator.
         The latter left with unsigned int __nocast; we might want to add a
         different type for those but for now let's leave them alone.  That,
         BTW, is a case when __nocast use had been actively confusing - it had
         been used in the same code for two different and similar types, with
         no way to catch misuses.  Switch of gfp_t to bitwise had caught that
         immediately...
      
      One tricky bit is left alone to be dealt with later - mapping->flags is
      a mix of gfp_t and error indications.  Left alone for now.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      27496a8c
  26. 11 10月, 2005 1 次提交
  27. 04 10月, 2005 1 次提交
    • D
      JFS: make special inodes play nicely with page balancing · ac17b8b5
      Dave Kleikamp 提交于
      This patch fixes up a few problems with jfs's reserved inodes.
      
      1. There is no need for the jfs code setting the I_DIRTY bits in i_state.
         I am ashamed that the code ever did this, and surprised it hasn't been
         noticed until now.
      
      2. Make sure special inodes are on an inode hash list.  If the inodes are
         unhashed, __mark_inode_dirty will fail to put the inode on the
         superblock's dirty list, and the data will not be flushed under memory
         pressure.
      
      3. Force writing journal data to disk when metapage_writepage is unable to
         write a metadata page due to pending journal I/O.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      ac17b8b5
  28. 21 9月, 2005 1 次提交
  29. 16 9月, 2005 1 次提交
  30. 10 9月, 2005 1 次提交
反馈
建议
客服 返回
顶部