linux-kernel - Re: [PATCH] x86/bugs: Adjust SRSO mitigation to new features

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: <ZyuJQlZqLS6K8zN2@google.com>
Date: Wed, 6 Nov 2024 07:20:34 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Borislav Petkov <bp@...nel.org>, X86 ML <x86@...nel.org>, Josh Poimboeuf <jpoimboe@...hat.com>, 
	Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, kvm@...r.kernel.org, 
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/bugs: Adjust SRSO mitigation to new features

On Tue, Nov 05, 2024, Borislav Petkov wrote:
> On Tue, Nov 05, 2024 at 11:18:16AM -0800, Sean Christopherson wrote:
> > It gets there, usually (as evidenced by my response).  But even for me, there's
> > a non-zero chance I'll miss something that's only Cc'd to kvm@, largely because
> > kvm@ is used by all things virt, i.e. it's a bit noisy:
> > 
> > $ git grep kvm@ MAINTAINERS | wc -l
> > 29
> 
> Hm, ok, so what do you guys prefer to be CCed on? Everyone from
> get_maintainer.pl's output? commit signers, authors, everyone? Or?

I prefer to be To:/Cc:'d on any patches that touch files that are covered by
relevant MAINTAINERS entries.  IMO, pulling names/emails from git is useless noise
the vast majority of the time.