[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 6 Apr 2016 22:49:55 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Yves-Alexis Perez <corsac@...ian.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Kees Cook <keescook@...omium.org>, Emrah Demir <ed@...sec.com>,
Dan Rosenberg <dan.j.rosenberg@...il.com>,
Dave Jones <davej@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Pavel Machek <pavel@...x.de>
Subject: Re: Re: [PATCH] KERNEL: resource: Fix bug on
leakage in /proc/iomem file
* Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> So yeah, maybe swap partitions are still more common than I thought. And I
> didn't even consider the possibility that people would hibernate a desktop like
> you do.
Also many distros will hibernate automatically on critically low battery (when
suspend won't save the system).
It would be much better to fix the kASLR/hibernation incompatibility ...
Just a random guess: much of the hibernation incompatibility comes from the fact
that on hibernation bootups the kASLR seed changes, which breaks hibernated kernel
addresses, right?
That should be easy to fix: if we added a kaslr_seed=xyz boot option, and added
that parmeter automatically (without showing it in /proc/cmdline ;-) on
hibernation bootups, we could solve much of the incompatibility, right?
This means that the first 'cold' bootup would set the kASLR seed - and subsequent
hibernated bootups would inherit it. That should be perfectly OK as long as we
don't expose the seed somewhere.
We could also write the kASLR seed to the hibernation image, but I don't think we
have the value available early enough - a boot option is better.
Thanks,
Ingo
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.
