lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 30 Aug 2016 16:35:05 +0800
From:   joeyli <jlee@...e.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Pavel Machek <pavel@....cz>, Chen Yu <yu.c.chen@...el.com>,
        linux-pm@...r.kernel.org, "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Lee@...gul.tnic
Subject: Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory
 map by md5 value

On Mon, Aug 29, 2016 at 03:41:23PM +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote:
> > Sounds about as easy as hot unplugging arbitrary memory address. IOW
> > "not easy".
> 
> Regardless, forcibly panicking the system more is still the wrong
> approach IMO.
> 
> Instead, I'd try to issue a big fat warning that BIOS corrupts E820 and
> that the user should disable hibernation on that box and never ever
> enable it again.
> 
> After that, the kernel should *disable* hibernation for the current boot
> so any further hibernation runs don't even happen. Maybe even taint
> itself.
>

I support this idea to disable hibernation when kernel detected e820 layout
was changed by BIOS. If system resume luckily then kernel should warn to user
and refuse to hibernate again. User must to know that's better to reboot
system when he saw the warning message after lucky resume.

Not just BIOS doesn't fix e820 layout. There have some machines doesn't provide
_S4_ function, so the hibernation fallbacks to "shutdown" mode because "platform"
mode unavailable. In this situation, user is just lucky to run the hibernation.
Kernel should warn to user and disable hibernation when detected e820 layout
changed.


Thanks a lot!
Joey Lee 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ