diff options
| author | Nick Piggin | 2006-09-26 08:31:24 +0200 |
|---|---|---|
| committer | Linus Torvalds | 2006-09-26 17:48:48 +0200 |
| commit | db37648cd6ce9b828abd6d49aa3d269926ee7b7d (patch) | |
| tree | a0155c7897f4706386d10c8718f98687bc357c82 /mm/slab.c | |
| parent | [PATCH] mm: remove_mapping() safeness (diff) | |
| download | kernel-qcow2-linux-db37648cd6ce9b828abd6d49aa3d269926ee7b7d.tar.gz kernel-qcow2-linux-db37648cd6ce9b828abd6d49aa3d269926ee7b7d.tar.xz kernel-qcow2-linux-db37648cd6ce9b828abd6d49aa3d269926ee7b7d.zip | |
[PATCH] mm: non syncing lock_page()
lock_page needs the caller to have a reference on the page->mapping inode
due to sync_page, ergo set_page_dirty_lock is obviously buggy according to
its comments.
Solve it by introducing a new lock_page_nosync which does not do a sync_page.
akpm: unpleasant solution to an unpleasant problem. If it goes wrong it could
cause great slowdowns while the lock_page() caller waits for kblockd to
perform the unplug. And if a filesystem has special sync_page() requirements
(none presently do), permanent hangs are possible.
otoh, set_page_dirty_lock() is usually (always?) called against userspace
pages. They are always up-to-date, so there shouldn't be any pending read I/O
against these pages.
Signed-off-by: Nick Piggin <npiggin@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'mm/slab.c')
0 files changed, 0 insertions, 0 deletions