Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 28 5月, 2011 1 次提交
  3. 26 5月, 2011 2 次提交
  5. 14 3月, 2011 1 次提交
  7. 03 3月, 2011 1 次提交
  9. 07 1月, 2011 5 次提交
  11. 26 10月, 2010 1 次提交
  13. 24 5月, 2010 1 次提交
    • J
      udf: Remove dead quota code · 36350462
      由 Jan Kara 提交于 
      Quota on UDF is non-functional at least since 2.6.16 (I'm too lazy to
do more archeology) because it does not provide .quota_write and .quota_read
functions and thus quotaon(8) just returns EINVAL. Since nobody complained
for all those years and quota support is not even in UDF standard just nuke
it.
Signed-off-by: NJan Kara <jack@suse.cz>
      36350462
  15. 22 5月, 2010 1 次提交
  17. 08 4月, 2010 1 次提交
  19. 05 3月, 2010 2 次提交
    • C
      dquot: cleanup dquot initialize routine · 871a2931
      由 Christoph Hellwig 提交于 
      Get rid of the initialize dquot operation - it is now always called from
the filesystem and if a filesystem really needs it's own (which none
currently does) it can just call into it's own routine directly.

Rename the now static low-level dquot_initialize helper to __dquot_initialize
and vfs_dq_init to dquot_initialize to have a consistent namespace.
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NJan Kara <jack@suse.cz>
      871a2931
    • C
      dquot: move dquot initialization responsibility into the filesystem · 907f4554
      由 Christoph Hellwig 提交于 
      Currently various places in the VFS call vfs_dq_init directly.  This means
we tie the quota code into the VFS.  Get rid of that and make the
filesystem responsible for the initialization.   For most metadata operations
this is a straight forward move into the methods, but for truncate and
open it's a bit more complicated.

For truncate we currently only call vfs_dq_init for the sys_truncate case
because open already takes care of it for ftruncate and open(O_TRUNC) - the
new code causes an additional vfs_dq_init for those which is harmless.

For open the initialization is moved from do_filp_open into the open method,
which means it happens slightly earlier now, and only for regular files.
The latter is fine because we don't need to initialize it for operations
on special files, and we already do it as part of the namespace operations
for directories.

Add a dquot_file_open helper that filesystems that support generic quotas
can use to fill in ->open.
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NJan Kara <jack@suse.cz>
      907f4554
  21. 04 3月, 2010 1 次提交
  23. 15 12月, 2009 1 次提交
    • J
      udf: Avoid IO in udf_clear_inode · 2c948b3f
      由 Jan Kara 提交于 
      It is not very good to do IO in udf_clear_inode. First, VFS does not really
expect inode to become dirty there and thus we have to write it ourselves,
second, memory reclaim gets blocked waiting for IO when it does not really
expect it, third, the IO pattern (e.g. on umount) resulting from writes in
udf_clear_inode is bad and it slows down writing a lot.

The reason why UDF needed to do IO in udf_clear_inode is that UDF standard
mandates extent length to exactly match inode size. But when we allocate
extents to a file or directory, we don't really know what exactly the final
file size will be and thus temporarily set it to block boundary and later
truncate it to exact length in udf_clear_inode. Now, this is changed to
truncate to final file size in udf_release_file for regular files. For
directories and symlinks, we do the truncation at the moment when learn
what the final file size will be.
Signed-off-by: NJan Kara <jack@suse.cz>
      2c948b3f
  25. 15 9月, 2009 1 次提交
  27. 02 4月, 2009 2 次提交
  29. 14 11月, 2008 1 次提交
  31. 23 10月, 2008 2 次提交
  33. 07 5月, 2008 2 次提交
  35. 28 4月, 2008 1 次提交
  37. 17 4月, 2008 4 次提交
  39. 09 2月, 2008 8 次提交
  41. 22 7月, 2007 1 次提交