From: Nikita Danilov Date: Sun, 1 May 2005 15:58:37 +0000 (-0700) Subject: [PATCH] doc: Locking update X-Git-Tag: v2.6.12-rc4~136^2~178 X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=2054606ad6dd6fee559fe790f190b15ed9355237;p=~shefty%2Frdma-dev.git [PATCH] doc: Locking update Make the Locking document truer. Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index a934baeeb33..1045da582b9 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking @@ -219,8 +219,12 @@ This may also be done to avoid internal deadlocks, but rarely. If the filesytem is called for sync then it must wait on any in-progress I/O and then start new I/O. -The filesystem should unlock the page synchronously, before returning -to the caller. +The filesystem should unlock the page synchronously, before returning to the +caller, unless ->writepage() returns special WRITEPAGE_ACTIVATE +value. WRITEPAGE_ACTIVATE means that page cannot really be written out +currently, and VM should stop calling ->writepage() on this page for some +time. VM does this by moving page to the head of the active list, hence the +name. Unless the filesystem is going to redirty_page_for_writepage(), unlock the page and return zero, writepage *must* run set_page_writeback() against the page,