From: Borislav Petkov <bp@alien8.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Chen Yu <yu.c.chen@intel.com>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org, Lee@nazgul.tnic,
Chun-Yi <jlee@suse.com>
Subject: Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value
Date: Mon, 29 Aug 2016 15:41:23 +0200 [thread overview]
Message-ID: <20160829134123.GA28806@nazgul.tnic> (raw)
In-Reply-To: <20160829071500.GA3859@amd>
On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote:
> Sounds about as easy as hot unplugging arbitrary memory address. IOW
> "not easy".
Regardless, forcibly panicking the system more is still the wrong
approach IMO.
Instead, I'd try to issue a big fat warning that BIOS corrupts E820 and
that the user should disable hibernation on that box and never ever
enable it again.
After that, the kernel should *disable* hibernation for the current boot
so any further hibernation runs don't even happen. Maybe even taint
itself.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-08-29 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 16:35 Chen Yu
2016-08-28 16:36 ` Pavel Machek
2016-08-29 4:59 ` Borislav Petkov
2016-08-29 7:15 ` Pavel Machek
2016-08-29 13:41 ` Borislav Petkov [this message]
2016-08-30 8:35 ` joeyli
2016-08-30 11:54 ` Rafael J. Wysocki
2016-09-08 21:15 ` Pavel Machek
2016-09-09 7:36 ` Chen Yu
2016-09-09 7:33 ` Pavel Machek
2016-08-30 11:51 ` Rafael J. Wysocki
2016-08-29 13:41 ` Rafael J. Wysocki
2016-08-29 15:13 ` Pavel Machek
2016-08-30 12:04 ` Rafael J. Wysocki
2016-08-30 19:53 ` Pavel Machek
2016-08-30 21:50 ` Rafael J. Wysocki
2016-08-31 11:03 ` Pavel Machek
2016-08-31 0:27 ` Rafael J. Wysocki
2016-08-31 11:07 ` Pavel Machek
2016-08-31 11:43 ` Pavel Machek
2016-08-31 11:54 ` Rafael J. Wysocki
2016-08-29 21:08 Prarit Bhargava
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=20160829134123.GA28806@nazgul.tnic \
--to=bp@alien8.de \
--cc=Lee@nazgul.tnic \
--cc=hpa@zytor.com \
--cc=jlee@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®