mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-11-18 23:54:26 +08:00
mm: try_to_unuse check removing right swap
There's a possible race in try_to_unuse() which Nick Piggin led me to two years ago. Where it does lock_page() after read_swap_cache_async(), what if another task removed that page from swapcache just before we locked it? It would sail though the (*swap_map > 1) tests doing nothing (because it could not have been removed from swapcache before its swap references were gone), until it reaches the delete_from_swap_cache(page) near the bottom. Now imagine that this page has been allocated to swap on a different swap area while we dropped page lock (perhaps at the top, perhaps in unuse_mm): we could wrongly remove from swap cache before the page has been written to swap, so a subsequent do_swap_page() would read in stale data from swap. I think this case could not happen before: remove_exclusive_swap_page() refused while page count was raised. But now with reuse_swap_page() and try_to_free_swap() removing from swap cache without minding page count, I think it could happen - the previous patch argued that it was safe because try_to_unuse() already ignored page count, but overlooked that it might be breaking the assumptions in try_to_unuse() itself. Signed-off-by: Hugh Dickins <hugh@veritas.com> Cc: Lee Schermerhorn <lee.schermerhorn@hp.com> Cc: Rik van Riel <riel@redhat.com> Cc: Nick Piggin <nickpiggin@yahoo.com.au> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: Robin Holt <holt@sgi.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
a2c43eed83
commit
68bdc8d647
@ -889,7 +889,16 @@ static int try_to_unuse(unsigned int type)
|
||||
lock_page(page);
|
||||
wait_on_page_writeback(page);
|
||||
}
|
||||
if (PageSwapCache(page))
|
||||
|
||||
/*
|
||||
* It is conceivable that a racing task removed this page from
|
||||
* swap cache just before we acquired the page lock at the top,
|
||||
* or while we dropped it in unuse_mm(). The page might even
|
||||
* be back in swap cache on another swap area: that we must not
|
||||
* delete, since it may not have been written out to swap yet.
|
||||
*/
|
||||
if (PageSwapCache(page) &&
|
||||
likely(page_private(page) == entry.val))
|
||||
delete_from_swap_cache(page);
|
||||
|
||||
/*
|
||||
|
Loading…
Reference in New Issue
Block a user