Re: [BUGFIX][PATCH] fix corruption of hibernation caused by reusing swap at saving image
From: Hugh Dickins
Date: Thu Aug 05 2010 - 15:13:12 EST
On Tue, Aug 3, 2010 at 7:46 PM, KAMEZAWA Hiroyuki
> On Wed, 4 Aug 2010 11:31:22 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>> On Wed, 4 Aug 2010 10:50:54 +0900
>> KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>> > This patch is created against 2.6.35. CC'ed stable.
>> > Thank you for all helps.
>> I'm sorry I now doubt this patch is wrong.
> Changed the description.
> Maybe the patch description/my understanding was wrong
> but the patch itself should work.
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
> Since 2.6.31, swap_map's refcounting was changed to show that
> a used swap entry is just for swap-cache, can be reused.
> Then, while scanning free entry in swap_map, a swap entry may
> be able to be reclaimed and reused. It was by the commit
> But this caused deta corruption at resume.
> The scenario is
> Â Â Â Â- Assume a clean-swap cache, but mapped.
> Â Â Â Â- at hibernation_snapshot, clean-swap-cache is saved as
> Â Â Â Â Âclean-swap-cache and swap_map is marked as SWAP_HAS_CACHE.
> Â Â Â Â- then, save_image() is called. And reuse SWAP_HAS_CACHE entry
> Â Â Â Â Âto save image, and break the contents.
> Â Â Â ÂAfter resume.
> Â Â Â Â- the memory reclaim runs and finds clean-not-referenced-swap-cache
> Â Â Â Â Âand discards it because it's marked as clean.
> Â Â Â Â ÂBut here, the contents on disk and swap-cache is inconsistent.
> Here, memory is corrupted.
Yes, that's the scenario: I thought that was what you meant by your
original description, but this more detailed description is a better
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/