linux-kernel - Re: [PATCH v9 00/17] Enable FSGSBASE instructions

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]

Message-ID: <20191115191200.GD22747@tassilo.jf.intel.com>
Date:   Fri, 15 Nov 2019 11:12:00 -0800
From:   Andi Kleen <ak@...ux.intel.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     "Chang S. Bae" <chang.seok.bae@...el.com>,
        linux-kernel@...r.kernel.org, bp@...en8.de, luto@...nel.org,
        hpa@...or.com, dave.hansen@...el.com, tony.luck@...el.com,
        ravi.v.shankar@...el.com, markus.t.metzger@...el.com
Subject: Re: [PATCH v9 00/17] Enable FSGSBASE instructions

On Fri, Nov 15, 2019 at 07:29:17PM +0100, Thomas Gleixner wrote:
> On Fri, 4 Oct 2019, Chang S. Bae wrote:
> > 
> > Updates from v8 [10]:
> > * Internalized the interrupt check in the helper functions (Andy L.)
> > * Simplified GS base helper functions (Tony L.)
> > * Changed the patch order to put the paranoid path changes before the
> >   context switch changes (Tony L.)
> > * Fixed typos (Randy D.) and massaged a few sentences in the documentation
> > * Massaged the FSGSBASE enablement message
> 
> That still lacks what Andy requested quite some time ago in the V8 thread:
> 
>      https://lore.kernel.org/lkml/034aaf3a-a93d-ec03-0bbd-068e1905b774@kernel.org/
> 
>   "I also think that, before this series can have my ack, it needs an 
>    actual gdb maintainer to chime in, publicly, and state that they have 
>    thought about and tested the ABI changes and that gdb still works on 
>    patched kernels with and without FSGSBASE enabled.  I realize that there 
>    were all kinds of discussions, but they were all quite theoretical, and 
>    I think that the actual patches need to be considered by people who 
>    understand the concerns.  Specific test cases would be nice, too."
> 
> What's the state of this?

Adding Markus.

-Andi