[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfaH2BHK==ZgbeajH8SxAxM51=91idrvd4n4L7UNiNQkEw@mail.gmail.com>
Date: Thu, 29 Feb 2024 11:53:56 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org, cve@...nel.org,
Jiri Kosina <jkosina@...e.cz>
Subject: Re: CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING
in raid5d"
On Thu, Feb 29, 2024 at 7:05 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> On Thu, Feb 29, 2024 at 06:32:03AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Feb 22, 2024 at 02:31:06PM +0100, Paolo Bonzini wrote:
> > > So if the reply-to points to LKML + the subsystem mailing
> > > list for the maintainers + a new ML for the security folks (and these three
> > > are also CC'd on the announcements, at least the last two), that would be
> > > nice to have. I can work on patches to vulns.git, for example to integrate
> > > with get_maintainer.pl, if you ack the idea.
> >
> > That might be a bit noisy, for some commits, but sure, I can see the
> > value in being notified about a CVE for my subsystem. If you have a
> > specific 'get_maintainer.pl' command line invocation you think would be
> > good, I can easily add it to the scripts.
>
> Would:
> --no-keywords --no-git --no-git-fallback --norolestats --nol
>
> be a good pattern to follow?
I would include lists as well. it would be nice to exclude
reviewed-bys but that's not easy to do in get_maintainer.pI
Paolo
Powered by blists - more mailing lists