Commit 2054606ad6dd6fee559fe790f190b15ed9355237

Authored by Nikita Danilov
Committed by Linus Torvalds
1 parent bd53b714d3

[PATCH] doc: Locking update

Make the Locking document truer.

Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Showing 1 changed file with 6 additions and 2 deletions Side-by-side Diff

Documentation/filesystems/Locking
... ... @@ -219,8 +219,12 @@
219 219 If the filesytem is called for sync then it must wait on any
220 220 in-progress I/O and then start new I/O.
221 221  
222   -The filesystem should unlock the page synchronously, before returning
223   -to the caller.
  222 +The filesystem should unlock the page synchronously, before returning to the
  223 +caller, unless ->writepage() returns special WRITEPAGE_ACTIVATE
  224 +value. WRITEPAGE_ACTIVATE means that page cannot really be written out
  225 +currently, and VM should stop calling ->writepage() on this page for some
  226 +time. VM does this by moving page to the head of the active list, hence the
  227 +name.
224 228  
225 229 Unless the filesystem is going to redirty_page_for_writepage(), unlock the page
226 230 and return zero, writepage *must* run set_page_writeback() against the page,