public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Balbir Singh <balbir@in.ibm.com>
Subject: Re: Memory corruption during hibernation since 2.6.31
Date: Thu, 5 Aug 2010 14:44:28 +0200	[thread overview]
Message-ID: <201008051444.32432.linux@rainbow-software.org> (raw)
In-Reply-To: <20100729142429.58b49dce.kamezawa.hiroyu@jp.fujitsu.com>

On Thursday 29 July 2010 07:24:29 KAMEZAWA Hiroyuki wrote:
> On Thu, 29 Jul 2010 14:23:33 +0900 (JST)
>
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > Can you please add explicit commenting in the code?
>
> How about this ?
> ==
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> At hibernation, all pages-should-be-saved are written into a image (here,
> swap). Then, swap_map[], memmap etcs are also saved into disks.
>
> But, swap allocation happens one by one. So, the final image of swap_map[]
> is different from saved one and the commit
> c9e444103b5e7a5a3519f9913f59767f92e33baf changes page's state while
> assiging swap. Because memory can be modified in hibernation is only
> not-to-be-save memory. it's a breakage.
>
> This patch fixes it by disabling swap entry reuse at hibernation.

6 days with no crash - so the patch seems to work.



> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
>  mm/swapfile.c |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.34.org/mm/swapfile.c
> ===================================================================
> --- linux-2.6.34.org.orig/mm/swapfile.c
> +++ linux-2.6.34.org/mm/swapfile.c
> @@ -315,8 +315,15 @@ checks:
>  	if (offset > si->highest_bit)
>  		scan_base = offset = si->lowest_bit;
>
> -	/* reuse swap entry of cache-only swap if not busy. */
> -	if (vm_swap_full() && si->swap_map[offset] == SWAP_HAS_CACHE) {
> +	/*
> + 	 * reuse swap entry of cache-only swap if not busy &&
> + 	 * when we're called via pageout(). At hibernation, swap-reuse
> + 	 * is harmful because it changes memory status...which may
> + 	 * be saved already.
> + 	 */
> +	if (vm_swap_full()
> +		&& usage == SWAP_HAS_CACHE
> +		&& si->swap_map[offset] == SWAP_HAS_CACHE) {
>  		int swap_was_freed;
>  		spin_unlock(&swap_lock);
>  		swap_was_freed = __try_to_reclaim_swap(si, offset);
>


-- 
Ondrej Zary

  parent reply	other threads:[~2010-08-05 12:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 21:20 Memory corruption during hibernation since 2.6.31 Ondrej Zary
2010-07-28 21:34 ` Rafael J. Wysocki
2010-07-28 21:38   ` Ondrej Zary
2010-07-29  1:06     ` KAMEZAWA Hiroyuki
2010-07-29  2:51       ` KAMEZAWA Hiroyuki
2010-07-29  4:23   ` KAMEZAWA Hiroyuki
2010-07-29  5:23     ` KOSAKI Motohiro
2010-07-29  5:24       ` KAMEZAWA Hiroyuki
2010-07-29  5:30         ` KOSAKI Motohiro
2010-07-29 17:33         ` Ondrej Zary
2010-07-29 18:44         ` Hugh Dickins
2010-07-29 18:55           ` Andrea Arcangeli
2010-07-29 23:40             ` Rafael J. Wysocki
2010-07-30  4:02               ` Hugh Dickins
2010-08-09  7:26             ` Pavel Machek
2010-07-29 23:29           ` Rafael J. Wysocki
2010-07-30  3:36             ` KAMEZAWA Hiroyuki
2010-07-30  3:54             ` Hugh Dickins
2010-07-30  0:01           ` KAMEZAWA Hiroyuki
2010-07-30  4:10             ` Hugh Dickins
2010-07-30  4:14               ` KAMEZAWA Hiroyuki
2010-07-30  4:46                 ` Hugh Dickins
2010-07-30 10:43                   ` KAMEZAWA Hiroyuki
2010-07-30 18:16                     ` Hugh Dickins
2010-08-02  6:02                 ` [RFC][PATCH -mm] hibernation: freeze swap at hibernation (Was " KAMEZAWA Hiroyuki
2010-08-02 14:27                   ` Rafael J. Wysocki
2010-08-02 15:59                   ` Balbir Singh
2010-08-03  0:19                     ` KAMEZAWA Hiroyuki
2010-08-03 23:09                   ` Rafael J. Wysocki
2010-08-03 23:31                     ` KAMEZAWA Hiroyuki
2010-08-04  2:26                       ` KAMEZAWA Hiroyuki
2010-08-04  4:57                       ` [PATCH -mm] hibernation: freeze swap at hibernation v2 KAMEZAWA Hiroyuki
2010-08-04 22:18                         ` Andrew Morton
2010-08-05  0:32                           ` KAMEZAWA Hiroyuki
2010-07-30  4:18           ` Memory corruption during hibernation since 2.6.31 Balbir Singh
2010-07-30  4:32             ` Hugh Dickins
2010-07-30  6:37               ` Balbir Singh
2010-08-05 12:44         ` Ondrej Zary [this message]
2010-08-03 10:50     ` Andrea Gelmini
2010-08-03 23:36       ` KAMEZAWA Hiroyuki
2010-08-04  1:50         ` [BUGFIX][PATCH] fix corruption of hibernation caused by reusing swap at saving image KAMEZAWA Hiroyuki
2010-08-04  2:31           ` KAMEZAWA Hiroyuki
2010-08-04  2:46             ` KAMEZAWA Hiroyuki
2010-08-05 19:12               ` Hugh Dickins
2010-08-05 11:41         ` Memory corruption during hibernation since 2.6.31 Andrea Gelmini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008051444.32432.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox