linux-kernel - Re: [PATCH v11 7/9] x86/traps: Communicate a LASS violation in #GP message

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: <9a4794f5-2a1f-4048-a870-b99fb5ab8136@intel.com>
Date: Fri, 31 Oct 2025 10:16:03 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sohil Mehta <sohil.mehta@...el.com>, x86@...nel.org,
 Dave Hansen <dave.hansen@...ux.intel.com>,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>
Cc: Jonathan Corbet <corbet@....net>, "H . Peter Anvin" <hpa@...or.com>,
 Andy Lutomirski <luto@...nel.org>, Josh Poimboeuf <jpoimboe@...nel.org>,
 Peter Zijlstra <peterz@...radead.org>, Ard Biesheuvel <ardb@...nel.org>,
 "Kirill A . Shutemov" <kas@...nel.org>, Xin Li <xin@...or.com>,
 David Woodhouse <dwmw@...zon.co.uk>, Sean Christopherson
 <seanjc@...gle.com>, Rick Edgecombe <rick.p.edgecombe@...el.com>,
 Vegard Nossum <vegard.nossum@...cle.com>,
 Andrew Cooper <andrew.cooper3@...rix.com>,
 Randy Dunlap <rdunlap@...radead.org>,
 Geert Uytterhoeven <geert@...ux-m68k.org>, Kees Cook <kees@...nel.org>,
 Tony Luck <tony.luck@...el.com>,
 Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-efi@...r.kernel.org
Subject: Re: [PATCH v11 7/9] x86/traps: Communicate a LASS violation in #GP
 message

On 10/29/25 14:03, Sohil Mehta wrote:
> To make the transition easier, enhance the #GP Oops message to include a
> hint about LASS violations. Also, add a special hint for kernel NULL
> pointer dereferences to match with the existing #PF message.

Reviewed-by: Dave Hansen <dave.hansen@...ux.intel.com>

This also reminds me... Are there tests for this somewhere? How did you
test all these new messages?