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 08:01:31 +0200 (CEST)
From: Jiri Kosina <>
To: Thomas Garnier <>
cc: "Rafael J . Wysocki" <>, Len Brown <>, 
    Pavel Machek <>,,,,,,
Subject: Re: [PATCH v1] x86/power/64: Restore processor state before using
 per-cpu variables

On Thu, 11 Aug 2016, 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 <>

Alright, this did the trick, thanks :) Feel free to add

	Reported-by: Jiri Kosina <>
	Tested-by: Jiri Kosina <>

One thing is still beyond me though ... how the heck this doesn't happen 
without DEBUG_LOCK_ALLOC? The percpu area pointer should be corrupted 
nevertheless, shouldn't it?


Jiri Kosina

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.