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: <d20a5e9d-dc0b-4bd2-89bb-95dbded8a581@intel.com>
Date: Thu, 30 Oct 2025 09:27:34 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>, 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>, 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 9/9] x86/cpu: Enable LASS by default during CPU
 initialization

On 10/30/25 01:40, H. Peter Anvin wrote:
> Legacy vsyscalls have been obsolete for how long now?

I asked Sohil to start throwing out all the non-essential bits from this
series. My thought was that we could get mainline so that LASS itself
could be enabled, even if it was in a somewhat weird config that a
distro would probably never do.

After that is merged, we can circle back and decide what to do with the
remaining bits like CR pinning and vsyscall emulation. I don't think any
of those bits will change the basic desire to have LASS support in the
kernel.

Does that sound like a sane approach to everyone?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ