Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 12 Aug 2016 09:03:52 -0700
From: Thomas Garnier <>
To: "Rafael J. Wysocki" <>
Cc: Borislav Petkov <>, "Rafael J . Wysocki" <>, Len Brown <>, 
	Pavel Machek <>, Linux PM <>, 
	Linux Kernel Mailing List <>, Kees Cook <>, 
	Kernel Hardening <>, Jiri Kosina <>, 
	Yinghai Lu <>
Subject: Re: [PATCH v1] x86/power/64: Restore processor state before using
 per-cpu variables

On Fri, Aug 12, 2016 at 4:14 AM, Rafael J. Wysocki <> wrote:
> On Fri, Aug 12, 2016 at 7:49 AM, Borislav Petkov <> wrote:
>> On Thu, Aug 11, 2016 at 02:49:29PM -0700, Thomas Garnier wrote:
>>> Restore the processor state before calling any other function to ensure
>>> per-cpu variables can be used with KASLR memory randomization.
>>> Tracing functions use per-cpu variables (gs based) and one was called
>>> just before restoring the processor state fully. It resulted in a double
>>> fault when both the tracing & the exception handler functions tried to
>>> use a per-cpu variable.
>>> Signed-off-by: Thomas Garnier <>
>>> ---
>>> Based on next-20160808
>> Ok, I believe before I test this, I need to apply another patch from
>> Rafael. I think it is the "Always create temporary identity mapping
>> correctly" thing.
>> Yes, no?
> Yes.
>> Rafael, can you please apply everything on a test branch for us to run?
> You can simply test my linux-next branch:
> git:// \
> linux-next
> That's 4.8-rc1 plus 3 fixes on top of it.

Borislav, let me know once you tested it and I will send a v2 with acked/tested.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.