Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 12 6月, 2009 3 次提交
    • A
      Push lock_super() into the ->remount_fs() of filesystems that care about it · bbd6851a
      由 Al Viro 提交于 
      Note that since we can't run into contention between remount_fs and write_super
(due to exclusion on s_umount), we have to care only about filesystems that
touch lock_super() on their own.  Out of those ext3, ext4, hpfs, sysv and ufs
do need it; fat doesn't since its ->remount_fs() only accesses assign-once
data (basically, it's "we have no atime on directories and only have atime on
files for vfat; force nodiratime and possibly noatime into *flags").

[folded a build fix from hch]
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      bbd6851a
    • C
      push BKL down into ->put_super · 6cfd0148
      由 Christoph Hellwig 提交于 
      Move BKL into ->put_super from the only caller.  A couple of
filesystems had trivial enough ->put_super (only kfree and NULLing of
s_fs_info + stuff in there) to not get any locking: coda, cramfs, efs,
hugetlbfs, omfs, qnx4, shmem, all others got the full treatment.  Most
of them probably don't need it, but I'd rather sort that out individually.
Preferably after all the other BKL pushdowns in that area.

[AV: original used to move lock_super() down as well; these changes are
removed since we don't do lock_super() at all in generic_shutdown_super()
now]
[AV: fuse, btrfs and xfs are known to need no damn BKL, exempt]
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      6cfd0148
    • C
      remove ->write_super call in generic_shutdown_super · 8c85e125
      由 Christoph Hellwig 提交于 
      We just did a full fs writeout using sync_filesystem before, and if
that's not enough for the filesystem it can perform it's own writeout
in ->put_super, which many filesystems already do.

Move a call to foofs_write_super into every foofs_put_super for now to
guarantee identical behaviour until it's cleaned up by the individual
filesystem maintainers.

Exceptions:

 - affs already has identical copy & pasted code at the beginning of
   affs_put_super so no need to do it twice.
 - xfs does the right thing without it and I have changes pending for
   the xfs tree touching this are so I don't really need conflicts
   here..
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      8c85e125
  3. 09 5月, 2009 1 次提交
  5. 03 4月, 2009 1 次提交
  7. 28 3月, 2009 4 次提交
  9. 26 3月, 2009 1 次提交
  11. 23 3月, 2009 1 次提交
  13. 22 1月, 2009 1 次提交
  15. 14 11月, 2008 1 次提交
  17. 23 10月, 2008 1 次提交
  19. 14 10月, 2008 1 次提交
  21. 05 8月, 2008 1 次提交
  23. 27 7月, 2008 1 次提交
  25. 26 7月, 2008 1 次提交
  27. 25 7月, 2008 1 次提交
  29. 13 5月, 2008 1 次提交
  31. 28 4月, 2008 4 次提交
  33. 20 3月, 2008 1 次提交
  35. 24 2月, 2008 1 次提交
  37. 09 2月, 2008 2 次提交
  39. 08 2月, 2008 1 次提交
  41. 06 12月, 2007 1 次提交
  43. 30 10月, 2007 1 次提交
  45. 17 10月, 2007 6 次提交
  47. 25 9月, 2007 1 次提交
  49. 20 7月, 2007 1 次提交
    • P
      mm: Remove slab destructors from kmem_cache_create(). · 20c2df83
      由 Paul Mundt 提交于 
      Slab destructors were no longer supported after Christoph's
c59def9f change. They've been
BUGs for both slab and slub, and slob never supported them
either.

This rips out support for the dtor pointer from kmem_cache_create()
completely and fixes up every single callsite in the kernel (there were
about 224, not including the slab allocator definitions themselves,
or the documentation references).
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      20c2df83
  51. 17 7月, 2007 1 次提交