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: <daa73e1b-2d1e-4b0b-a7c6-1f909c9672ba@intel.com>
Date: Fri, 20 Jun 2025 15:46:11 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>
Cc: acme@...hat.com, aik@....com, akpm@...ux-foundation.org,
 alexander.shishkin@...ux.intel.com, ardb@...nel.org, ast@...nel.org,
 bp@...en8.de, brijesh.singh@....com, changbin.du@...wei.com,
 christophe.leroy@...roup.eu, corbet@....net, daniel.sneddon@...ux.intel.com,
 dave.hansen@...ux.intel.com, ebiggers@...gle.com, geert+renesas@...der.be,
 houtao1@...wei.com, hpa@...or.com, jgg@...pe.ca, jgross@...e.com,
 jpoimboe@...nel.org, kai.huang@...el.com, kees@...nel.org,
 kirill.shutemov@...ux.intel.com, leitao@...ian.org,
 linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux@...musvillemoes.dk,
 luto@...nel.org, mcgrof@...nel.org, mhiramat@...nel.org,
 michael.roth@....com, mingo@...nel.org, mingo@...hat.com,
 namhyung@...nel.org, paulmck@...nel.org, pawan.kumar.gupta@...ux.intel.com,
 peterz@...radead.org, rick.p.edgecombe@...el.com, rppt@...nel.org,
 sandipan.das@....com, shijie@...amperecomputing.com, sohil.mehta@...el.com,
 tglx@...utronix.de, tj@...nel.org, tony.luck@...el.com,
 vegard.nossum@...cle.com, x86@...nel.org, xin3.li@...el.com,
 xiongwei.song@...driver.com, ytcoode@...il.com
Subject: Re: [PATCHv6 00/16] x86: Enable Linear Address Space Separation
 support

On 6/20/25 15:04, Andrew Cooper wrote:
>> Most of the cover letter here reads like an Intel whitepaper. That's not
>> the worst thing in the world, but I think it glosses over one very
>> important point:
>>
>> 	Had it been available, LASS alone would have mitigated Meltdown.
>>
>> Could we say this up front in a prominent place, please?
> 
> I'm going to nitpick. :)
> 
> Yes, LASS would have made Meltdown a far less major problem than it was,
> but I don't think that phrasing is fair.  As I recall, LASS was
> literally invented as a "what would have been useful?" exercise in the
> wake of Meltdown.

While being concise, I was also trying to convey that LASS is pretty
powerful, rather than it being some uniquely genius move by the CPU
designers. It was absolutely conceived of in hindsight.

Do you feel like the changelog is sufficient as-is? Or do you think we
can beef the changelog up a bit? I just want to make sure folks reading
it have a clear understanding that it's not fixing purely theoretical
issues.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ