diff options
Diffstat (limited to 'Documentation/filesystems/Locking')
| -rw-r--r-- | Documentation/filesystems/Locking | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index a934baeeb33a..1045da582b9b 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking | |||
| @@ -219,8 +219,12 @@ This may also be done to avoid internal deadlocks, but rarely. | |||
| 219 | If the filesytem is called for sync then it must wait on any | 219 | If the filesytem is called for sync then it must wait on any |
| 220 | in-progress I/O and then start new I/O. | 220 | in-progress I/O and then start new I/O. |
| 221 | 221 | ||
| 222 | The filesystem should unlock the page synchronously, before returning | 222 | The filesystem should unlock the page synchronously, before returning to the |
| 223 | to the caller. | 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 | Unless the filesystem is going to redirty_page_for_writepage(), unlock the page | 229 | Unless the filesystem is going to redirty_page_for_writepage(), unlock the page |
| 226 | and return zero, writepage *must* run set_page_writeback() against the page, | 230 | and return zero, writepage *must* run set_page_writeback() against the page, |
