1. 30 May, 2006 3 commits
  2. 22 Apr, 2006 1 commit
  3. 21 Apr, 2006 1 commit
  4. 26 Mar, 2006 1 commit
  5. 23 Mar, 2006 1 commit
  6. 03 Mar, 2006 1 commit
  7. 02 Mar, 2006 1 commit
  8. 28 Feb, 2006 2 commits
  9. 15 Feb, 2006 1 commit
  10. 27 Jan, 2006 1 commit
  11. 18 Jan, 2006 1 commit
  12. 12 Jan, 2006 1 commit
  13. 09 Jan, 2006 1 commit
    • OGAWA Hirofumi's avatar
      [PATCH] Fix and add EXPORT_SYMBOL(filemap_write_and_wait) · 28fd1298
      OGAWA Hirofumi authored
      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: default avatarTrond Myklebust <trond.myklebust@fys.uio.no>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      28fd1298
  14. 13 Dec, 2005 1 commit
  15. 02 Dec, 2005 1 commit
  16. 18 Nov, 2005 1 commit
  17. 20 Oct, 2005 1 commit
  18. 12 Oct, 2005 2 commits
  19. 10 Oct, 2005 1 commit
  20. 06 Oct, 2005 1 commit
  21. 05 Oct, 2005 3 commits
  22. 03 Oct, 2005 1 commit
  23. 16 Sep, 2005 2 commits
  24. 01 Sep, 2005 1 commit
  25. 31 Aug, 2005 1 commit
  26. 30 Aug, 2005 1 commit
  27. 26 Aug, 2005 1 commit
    • Steve French's avatar
      [PATCH] Fix oops in fs/locks.c on close of file with pending locks · d634cc15
      Steve French authored
      The recent change to locks_remove_flock code in fs/locks.c changes how
      byte range locks are removed from closing files, which shows up a bug in
      cifs.
      
      The assumption in the cifs code was that the close call sent to the
      server would remove any pending locks on the server on this file, but
      that is no longer safe as the fs/locks.c code on the client wants unlock
      of 0 to PATH_MAX to remove all locks (at least from this client, it is
      not possible AFAIK to remove all locks from other clients made to the
      server copy of the file).
      
      Note that cifs locks are different from posix locks - and it is not
      possible to map posix locks perfectly on the wire yet, due to
      restrictions of the cifs network protocol, even to Samba without adding
      a new request type to the network protocol (which we plan to do for
      Samba 3.0.21 within a few months), but the local client will have the
      correct, posix view, of the lock in most cases.
      
      The correct fix for cifs for this would involve a bigger change than I
      would like to do this late in the 2.6.13-rc cycle - and would involve
      cifs keeping track of all unmerged (uncoalesced) byte range locks for
      each remote inode and scanning that list to remove locks that intersect
      or fall wholly within the range - locks that intersect may have to be
      reaquired with the smaller, remaining range.
      Signed-off-by: default avatarSteve French <sfrench@us.ibm.com>
      Signed-off-by: default avatarDave Kleikamp <shaggy@austin.ibm.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      d634cc15
  28. 25 Aug, 2005 1 commit
  29. 24 Aug, 2005 1 commit
  30. 21 Aug, 2005 1 commit
  31. 24 Jun, 2005 1 commit
  32. 23 Jun, 2005 1 commit
  33. 13 Jun, 2005 1 commit