Skip to content

K
Kernel

openeuler / Kernel
大约 1 年 前同步成功

通知 7
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 13 7月, 2007 1 次提交
  3. 12 7月, 2007 1 次提交
  5. 10 7月, 2007 1 次提交
  7. 25 6月, 2007 1 次提交
  9. 09 5月, 2007 1 次提交
  11. 03 5月, 2007 1 次提交
  13. 05 4月, 2007 1 次提交
  15. 03 4月, 2007 1 次提交
  17. 06 3月, 2007 1 次提交
  19. 27 2月, 2007 1 次提交
  21. 17 2月, 2007 1 次提交
  23. 09 2月, 2007 1 次提交
  25. 02 2月, 2007 1 次提交
  27. 24 12月, 2006 1 次提交
  29. 11 12月, 2006 1 次提交
    • A
      [PATCH] io-accounting-read-accounting cifs fix · 6f88cc2e
      由 Andrew Morton 提交于 
      CIFS implements ->readpages and doesn't use read_cache_pages().  So wire the
read IO accounting up within CIFS.

Cc: Jay Lan <jlan@sgi.com>
Cc: Shailabh Nagar <nagar@watson.ibm.com>
Cc: Balbir Singh <balbir@in.ibm.com>
Cc: Chris Sturtivant <csturtiv@sgi.com>
Cc: Tony Ernst <tee@sgi.com>
Cc: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: Steven French <sfrench@us.ibm.com>
Cc: David Wright <daw@sgi.com>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6f88cc2e
  31. 09 12月, 2006 1 次提交
  33. 10 11月, 2006 1 次提交
  35. 08 11月, 2006 1 次提交
  37. 04 11月, 2006 1 次提交
  39. 01 10月, 2006 1 次提交
  41. 21 9月, 2006 1 次提交
  43. 12 8月, 2006 2 次提交
  45. 01 7月, 2006 1 次提交
  47. 29 6月, 2006 1 次提交
  49. 26 6月, 2006 1 次提交
  51. 23 6月, 2006 2 次提交
    • M
      [PATCH] vfs: add lock owner argument to flush operation · 75e1fcc0
      由 Miklos Szeredi 提交于 
      Pass the POSIX lock owner ID to the flush operation.

This is useful for filesystems which don't want to store any locking state
in inode->i_flock but want to handle locking/unlocking POSIX locks
internally.  FUSE is one such filesystem but I think it possible that some
network filesystems would need this also.

Also add a flag to indicate that a POSIX locking request was generated by
close(), so filesystems using the above feature won't send an extra locking
request in this case.
Signed-off-by: NMiklos Szeredi <miklos@szeredi.hu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      75e1fcc0
    • O
      [PATCH] writeback: fix range handling · 111ebb6e
      由 OGAWA Hirofumi 提交于 
      When a writeback_control's `start' and `end' fields are used to
indicate a one-byte-range starting at file offset zero, the required
values of .start=0,.end=0 mean that the ->writepages() implementation
has no way of telling that it is being asked to perform a range
request.  Because we're currently overloading (start == 0 && end == 0)
to mean "this is not a write-a-range request".

To make all this sane, the patch changes range of writeback_control.

So caller does: If it is calling ->writepages() to write pages, it
sets range (range_start/end or range_cyclic) always.

And if range_cyclic is true, ->writepages() thinks the range is
cyclic, otherwise it just uses range_start and range_end.

This patch does,

    - Add LLONG_MAX, LLONG_MIN, ULLONG_MAX to include/linux/kernel.h
      -1 is usually ok for range_end (type is long long). But, if someone did,

		range_end += val;		range_end is "val - 1"
		u64val = range_end >> bits;	u64val is "~(0ULL)"

      or something, they are wrong. So, this adds LLONG_MAX to avoid nasty
      things, and uses LLONG_MAX for range_end.

    - All callers of ->writepages() sets range_start/end or range_cyclic.

    - Fix updates of ->writeback_index. It seems already bit strange.
      If it starts at 0 and ended by check of nr_to_write, this last
      index may reduce chance to scan end of file.  So, this updates
      ->writeback_index only if range_cyclic is true or whole-file is
      scanned.
Signed-off-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Nathan Scott <nathans@sgi.com>
Cc: Anton Altaparmakov <aia21@cantab.net>
Cc: Steven French <sfrench@us.ibm.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      111ebb6e
  53. 07 6月, 2006 1 次提交
  55. 02 6月, 2006 1 次提交
  57. 01 6月, 2006 1 次提交
  59. 31 5月, 2006 4 次提交
  61. 22 4月, 2006 2 次提交
  63. 27 3月, 2006 1 次提交
  65. 23 3月, 2006 1 次提交
  67. 04 3月, 2006 1 次提交