Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 11 Aug 2016 02:35:48 +0200
From: "Rafael J. Wysocki" <>
To: Jiri Kosina <>, Thomas Garnier <>
Cc: Borislav Petkov <>, "Rafael J. Wysocki" <>, 
	Linux PM list <>, "the arch/x86 maintainers" <>, 
	Linux Kernel Mailing List <>, Yinghai Lu <>, 
	Thomas Gleixner <>, Ingo Molnar <>, "H . Peter Anvin" <>, 
	Kees Cook <>, Pavel Machek <>, 
	Kernel Hardening <>
Subject: Re: [Resend][PATCH] x86/power/64: Always create temporary identity
 mapping correctly

On Wed, Aug 10, 2016 at 11:59 PM, Jiri Kosina <> wrote:
> On Wed, 10 Aug 2016, Rafael J. Wysocki wrote:
>> So I used your .config to generate one for my test machine and with
>> that I can reproduce.
> Was that the config I've sent, or did Boris provide one as well? Which one
> are you able to reproduce with please?

It's the Boris' one.

Moreover, I have found the options that make the difference: unsetting
unset CONFIG_LOCKDEP AFAICS) in it makes hibernation work again with
CONFIG_RANDOMIZE_MEMORY set and with the $subject patch applied.

Unbelievable, but that's what I'm seeing.

Now, that leads to a few questions:

- How does lockdep change the picture so it matters for hibernation?
- Why is hibernation the only piece that's affected?
- Why is RANDOMIZE_MEMORY necessary to make this breakage show up?

Thomas, any ideas?


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.