linux-kernel - Re: [PATCH v3 00/35] x86/bugs: Attack vector controls

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]

Message-ID: <20250113174144.ixp5raixrk2gpbvm@desk>
Date: Mon, 13 Jan 2025 09:41:44 -0800
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: David Kaplan <david.kaplan@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Josh Poimboeuf <jpoimboe@...nel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
	"H . Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/35] x86/bugs: Attack vector controls

On Sun, Jan 12, 2025 at 12:38:18PM +0100, Borislav Petkov wrote:
> For some reason your mail client is mangling your mails and they land in spam.
> And they're not even on lore. Here's what I got from you:
> 
> ...
> Date: Fri, 10 Jan 2025 09:14:10 -0800
> From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, To:
>         Borislav Petkov <bp@...en8.de>;
> Cc: David Kaplan <david.kaplan@....com>,
> ...
> 
> The "To:" is not on a new line but separate with a "," from the "From:" and
> that confuses mail clients perhaps.

That is strange. Looks like this is randomly happening, some of the emails
I checked on lore looks fine. I am using an old version of neomutt, will
update it and see if it fixes the issue.

> On Fri, Jan 10, 2025 at 09:14:10AM -0800, Pawan Gupta wrote:
> > Mitigation setup is done too early for tracing to be of any help. A few
> > extra debug prints is what I can think of.
> 
> That's what I mean - no tracing. A couple of verbose, properly placed printks
> to help show what gets called when and which are enabled with a cmdline param.
> 
> mitigations=debug
> 
> or so.

Sure, I will add some debug prints to help understand the flow.