linux-kernel - Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

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:   Mon, 25 Dec 2017 10:47:46 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Alexandru Chirvasitu <achirvasub@...il.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        kernel list <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        Brian Gerst <brgerst@...il.com>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot


* Alexandru Chirvasitu <achirvasub@...il.com> wrote:

> The first attachment is the config I initially used last night after
> that second patch (removing 'local' etc.).
> 
> As you guessed, all four options are set, hence the name of the file
> (ending in '-y'). The other config I'm attaching was treated as you
> lay out (2-config-n).
> 
> I used the '-n' config to compile two kernels just now:
> 
> (a) e802a51, that same first commit giving me trouble.
> 
> The changes made no difference to kexec behaviour: with the e802a51
> kernel calling kexec boot directly with -e and triggering a panic both
> kick off a full reboot, though the crash kernel registers as loaded.
> 
> (b) the kernel in the branch I made last night, with the set_idt kexec
> (for good measure, I thought I might as well do this one too).
> 
> No difference here either: the crash dump kernel boots fine both ways
> (directly and upon intentional crashing).

Thanks for all the info!

Detailed analysis from me (or Thomas) will have to wait after the Christmas 
hollidays.

Thanks,

	Ingo