From: Baoquan He <bhe@redhat.com>
To: keescook@chromium.org
Cc: linux-kernel@vger.kernel.org, rafael.j.wysocki@intel.com
Subject: About commit 65fe935d ("x86/KASLR, x86/power: Remove x86 hibernation restrictions")
Date: Sun, 22 Jan 2017 18:53:18 +0800 [thread overview]
Message-ID: <20170122105318.GD5672@x1> (raw)
Hi Kees,
In your commit 65fe935dd, you mentioned with the fix of 70595b479ce1,
the x86 hibernation restrictions can be removed. However I didn't find
it in Linus's tree. I found commit 65c0554 ("x86/power/64: Fix kernel text
mapping corruption during image restoration"), it should be the one you
mentioned, but not very sure since it was merged later than your commit.
Could you help confirm this?
commit 65fe935dd2387a4faf15314c73f5e6d31ef0217e
Author: Kees Cook <keescook@chromium.org>
Date: Mon Jun 13 15:10:02 2016 -0700
x86/KASLR, x86/power: Remove x86 hibernation restrictions
With the following fix:
70595b479ce1 ("x86/power/64: Fix crash whan the hibernation code passes control to the image kernel")
... there is no longer a problem with hibernation resuming a
KASLR-booted kernel image, so remove the restriction.
commit 65c0554b73c920023cc8998802e508b798113b46
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Thu Jun 30 18:11:41 2016 +0200
x86/power/64: Fix kernel text mapping corruption during image restoration
Logan Gunthorpe reports that hibernation stopped working reliably for
him after commit ab76f7b4ab23 (x86/mm: Set NX on gap between __ex_table
and rodata).
Thanks
Baoquan
next reply other threads:[~2017-01-22 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 10:53 Baoquan He [this message]
2017-01-26 1:06 ` About commit 65fe935d ("x86/KASLR, x86/power: Remove x86 hibernation restrictions") Kees Cook
2017-01-26 1:16 ` Baoquan He
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=20170122105318.GD5672@x1 \
--to=bhe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@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