From 2ab14f6d303dff51472901c8139d4ec7ebafc778 Mon Sep 17 00:00:00 2001 From: Nikita Danilov Date: Sun, 1 May 2005 08:58:37 -0700 Subject: [PATCH] --- yaml --- r: 629 b: refs/heads/master c: 2054606ad6dd6fee559fe790f190b15ed9355237 h: refs/heads/master i: 627: e2a13007cc90c98c4205f8fde590778095af3f5c v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/Locking | 8 ++++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 56c44bbebcac..9d464c3b3731 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: bd53b714d32a29bdf33009f812e295667e92b930 +refs/heads/master: 2054606ad6dd6fee559fe790f190b15ed9355237 diff --git a/trunk/Documentation/filesystems/Locking b/trunk/Documentation/filesystems/Locking index a934baeeb33a..1045da582b9b 100644 --- a/trunk/Documentation/filesystems/Locking +++ b/trunk/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,