Revision 5a6d41b32a17ca902ef50fdfa170d7f23264bad5 authored by Trond Myklebust on 14 April 2007, 23:10:12 UTC, committed by Linus Torvalds on 15 April 2007, 04:46:48 UTC
If the writebacks are cancelled via nfs_cancel_dirty_list, or due to the memory allocation failing in nfs_flush_one/nfs_flush_multi, then we must ensure that the PG_writeback flag is cleared. Also ensure that we actually own the PG_writeback flag whenever we schedule a new writeback by making nfs_set_page_writeback() return the value of test_set_page_writeback(). The PG_writeback page flag ends up replacing the functionality of the PG_FLUSHING nfs_page flag, so we rip that out too. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent 60fa3f7
File | Mode | Size |
---|---|---|
Makefile | -rw-r--r-- | 161 bytes |
README | -rw-r--r-- | 279 bytes |
bitmap.c | -rw-r--r-- | 3.6 KB |
dir.c | -rw-r--r-- | 2.5 KB |
file.c | -rw-r--r-- | 916 bytes |
fsync.c | -rw-r--r-- | 3.0 KB |
inode.c | -rw-r--r-- | 15.0 KB |
namei.c | -rw-r--r-- | 5.6 KB |
truncate.c | -rw-r--r-- | 727 bytes |
Computing file changes ...