linux-kernel - Re: [patch 15/16] x86/entry: Switch page fault exceptions to idtentry

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] [day] [month] [year] [list]

Date:   Fri, 06 Mar 2020 00:02:12 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Andy Lutomirski <luto@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     x86@...nel.org, Steven Rostedt <rostedt@...dmis.org>,
        Brian Gerst <brgerst@...il.com>,
        Juergen Gross <jgross@...e.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [patch 15/16] x86/entry: Switch page fault exceptions to idtentry_simple

Andy Lutomirski <luto@...nel.org> writes:

> On 2/25/20 2:33 PM, Thomas Gleixner wrote:
>> Convert page fault exceptions to IDTENTRY_CR2:
>>   - Implement the C entry point with DEFINE_IDTENTRY
>>   - Emit the ASM stub with DECLARE_IDTENTRY
>>   - Remove the ASM idtentry in 64bit
>>   - Remove the CR2 read from 64bit
>>   - Remove the open coded ASM entry code in 32bit
>>   - Fixup the XEN/PV code
>>   - Remove the old prototyoes
>
> $SUBJECT says idtentry_simple.  I think you meant IDTENTRY_CR2.

Yes.

> (I typed this a while ago and apparently failed to hit send.  I'm not
> sure it's still relevant.)

No, as we agreed to create raw IDTENTRY points for stuff which does not
fall into the trivial category.

I've reworked the mess, but now I'm tripping over the brilliant stuff in
that async PF code. The rcu_irq_enter()/exit() dance there is really
great and of course done unconditionally even if called from the VM exit
PF handling code. Oh well...

Thanks,

        tglx