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] [day] [month] [year] [list]
Date: Tue, 30 Apr 2024 06:12:42 -0700
From: Breno Leitao <leitao@...ian.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: jpoimboe@...nel.org, mingo@...hat.com, tglx@...utronix.de, bp@...en8.de,
	x86@...nel.org, leit@...a.com, linux-kernel@...r.kernel.org,
	pawan.kumar.gupta@...ux.intel.com, bpf@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v6 00/13] x86/bugs: Add a separate config for each
 mitigation

Hello Ingo,

On Wed, Jan 10, 2024 at 07:07:48PM +0100, Ingo Molnar wrote:
> 
> * Breno Leitao <leitao@...ian.org> wrote:
> 
> > > Yeah, so:
> > > 
> > >  - I took this older series and updated it to current upstream, and made
> > >    sure all renames were fully done: there were two new Kconfig option
> > >    uses, which I integrated into the series. (Sorry about the delay, holiday & stuff.)
> > > 
> > >  - I also widened the renames to comments and messages, which were not
> > >    always covered.
> > > 
> > >  - Then I took this cover letter and combined it with a more high level
> > >    description of the reasoning behind this series I wrote up, and added it
> > >    to patch #1. (see it below.)
> > > 
> > >  - Then I removed the changelog repetition from the other patches and just
> > >    referred them back to patch #1.
> > > 
> > >  - Then I stuck the resulting updated series into tip:x86/bugs, without the 
> > >    last 3 patches that modify behavior.
> > 
> > Thanks for your work. I am currently reviwing the tip branch and the
> > merge seems go so far.
> > 
> > Regarding the last 3 patches, what are the next steps?
> 
> Please resubmit them in a few days (with Josh's Acked-by added and any 
> fixes/enhancements done along the way), on top of tip:x86/bugs.

I've sent the commits on top of the latest mitigations. Have you had a
chance to see them?

	https://lore.kernel.org/all/20240422165830.2142904-1-leitao@debian.org/

PS: I took the opportunity to break them down, one per mitigation, so, it
could simplify the patch management.

Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ