linux-kernel - Re: [RESEND PATCH v6] x86/fpu: Trying to fix writing PKRU through ptrace

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, 7 Nov 2022 12:52:52 -0800
From:   Dave Hansen <dave.hansen@...el.com>
To:     Slade Watkins <srw@...dewatkins.net>, Kyle Huey <me@...ehuey.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
        x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Andy Lutomirski <luto@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Sean Christopherson <seanjc@...gle.com>,
        linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
        Robert O'Callahan <robert@...llahan.org>,
        David Manouchehri <david.manouchehri@...eup.net>
Subject: Re: [RESEND PATCH v6] x86/fpu: Trying to fix writing PKRU through
 ptrace

On 11/7/22 12:49, Slade Watkins wrote:
> On Mon, Nov 7, 2022 at 1:38 AM Kyle Huey <me@...ehuey.com> wrote:
>> I've been trying since July to get this regression that was introduced in
>> 5.14 fixed. This is my third time submitting this version of the patch in the
>> last two months. Both prior submissions have not received any comments from
>> (nor have they been applied by) the x86 maintainers. I don't really know
>> what else to do at this point beyond "complain to the management" as it
>> were.
>>
>> I appreciate anything you can do to unjam things here.
> Maintainers: is there any reason why this hasn't been applied, or
> received comments? I'm confused and a bit worried.

Thomas had some strong opinions in the area, so I've been neglecting it.
 I'll put it in my queue to take a look now, though.