An error occurred fetching the project authors.
  1. 18 Jul, 2007 1 commit
  2. 17 Jul, 2007 1 commit
  3. 16 Jul, 2007 1 commit
  4. 13 Jul, 2007 1 commit
  5. 11 Jul, 2007 1 commit
  6. 10 Jul, 2007 1 commit
  7. 24 Jun, 2007 1 commit
  8. 08 May, 2007 1 commit
  9. 03 May, 2007 1 commit
  10. 04 Apr, 2007 1 commit
  11. 02 Apr, 2007 1 commit
  12. 06 Mar, 2007 1 commit
  13. 26 Feb, 2007 1 commit
  14. 17 Feb, 2007 1 commit
  15. 08 Feb, 2007 1 commit
  16. 02 Feb, 2007 1 commit
  17. 24 Dec, 2006 1 commit
  18. 10 Dec, 2006 1 commit
    • Andrew Morton's avatar
      [PATCH] io-accounting-read-accounting cifs fix · 6f88cc2e
      Andrew Morton authored
      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: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      6f88cc2e
  19. 08 Dec, 2006 1 commit
  20. 09 Nov, 2006 1 commit
  21. 07 Nov, 2006 1 commit
  22. 03 Nov, 2006 1 commit
  23. 30 Sep, 2006 1 commit
  24. 21 Sep, 2006 1 commit
  25. 11 Aug, 2006 2 commits
  26. 30 Jun, 2006 1 commit
  27. 28 Jun, 2006 1 commit
  28. 26 Jun, 2006 1 commit
  29. 23 Jun, 2006 2 commits
    • Miklos Szeredi's avatar
      [PATCH] vfs: add lock owner argument to flush operation · 75e1fcc0
      Miklos Szeredi authored
      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: default avatarMiklos Szeredi <miklos@szeredi.hu>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      75e1fcc0
    • OGAWA Hirofumi's avatar
      [PATCH] writeback: fix range handling · 111ebb6e
      OGAWA Hirofumi authored
      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: default avatarOGAWA 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: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      111ebb6e
  30. 07 Jun, 2006 1 commit
  31. 01 Jun, 2006 1 commit
  32. 31 May, 2006 1 commit
  33. 30 May, 2006 4 commits
  34. 22 Apr, 2006 1 commit
  35. 21 Apr, 2006 1 commit