linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chen Yu <yu.c.chen@intel.com>
Cc: rjw@rjwysocki.net, len.brown@intel.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, rui.zhang@intel.com, jlee@suse.com,
	joeyli.kernel@gmail.com, yinghai@kernel.org
Subject: Re: [PATCH] [v4] PM / hibernate: Fix hibernation panic caused by inconsistent e820 map
Date: Thu, 17 Sep 2015 08:07:35 +0200	[thread overview]
Message-ID: <20150917060735.GF6665@amd> (raw)
In-Reply-To: <1442425343-8339-1-git-send-email-yu.c.chen@intel.com>

> v3:
>  - Adjust the logic to exclude the end_pfn boundary in pfn_mapped
>    when invoking mark_valid_pages, because the end_pfn is not
>    a mapped page frame, we should not regard it as a valid page.
> 
>    Move the sanity check of valid pages to a early stage in resuming
>    process(moved to mark_unsafe_pages), in this way, we can avoid
>    unnecessarily accessing these invalid pages in later stage(yes,
>    move to the original position Joey once introduced in:
>    Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
>    reserved regions")
> 
>    With v3 patch applied, I did 30 cycles on my problematic platform,
>    no panic triggered anymore(50% reproducible before patched, by
>    plugging/unplugging memory peripheral during hibernation), and it
>    just warns of invalid pages.

NAK. Turning panic into data corruption is a bad idea.

> +	if (!swsusp_page_is_valid(pfn_to_page(pfn))) {
> +		pr_err(
> +		"PM: Hibernation failed, address %#010llx to restored not valid!\n",
> +			(unsigned long long) pfn << PAGE_SHIFT);

...and still bad english.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-09-17  6:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 17:42 [PATCH] [v4] PM / hibernate: Fix hibernation panic caused by inconsistent e820 map Chen Yu
2015-09-17  6:07 ` Pavel Machek [this message]
2015-09-17 18:11   ` Chen, Yu C
2015-09-17 20:43     ` Pavel Machek
2015-09-18  3:47       ` Chen, Yu C
2015-09-18  5:47         ` Pavel Machek
2015-09-18  6:11           ` Chen, Yu C
2015-10-04 15:15             ` Pavel Machek
2015-10-09  9:32               ` Chen, Yu C
2015-09-17 18:21   ` Chen, Yu C

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=20150917060735.GF6665@amd \
    --to=pavel@ucw.cz \
    --cc=jlee@suse.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=yinghai@kernel.org \
    --cc=yu.c.chen@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).