From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, cve@kernel.org,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"
Date: Thu, 29 Feb 2024 07:05:02 +0100 [thread overview]
Message-ID: <2024022918-deepen-composed-c680@gregkh> (raw)
In-Reply-To: <2024022949-uncapped-crushing-e5f9@gregkh>
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?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-29 6:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 18:34 CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" Greg Kroah-Hartman
2024-02-21 9:09 ` CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" [resend] Paolo Bonzini
[not found] ` <CABgObfYDcFPRNpGtsY=UbstXbqVCMcxy3LPS_xJ65aFcByC=Nw@mail.gmail.com>
[not found] ` <ZdXt09vL4GJy6PbP@sashalap>
[not found] ` <0e8675e0-165d-4cf7-9755-666278868ab8@redhat.com>
[not found] ` <ZdX2LcAWR6wyvYC5@sashalap>
[not found] ` <bec7c1db-c13e-4b00-a968-4ae69539d7ac@redhat.com>
2024-02-21 14:35 ` CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" Sasha Levin
2024-02-21 15:02 ` Paolo Bonzini
2024-02-21 15:11 ` Sasha Levin
2024-02-21 15:56 ` Paolo Bonzini
2024-02-21 16:22 ` Sasha Levin
2024-02-21 18:09 ` Paolo Bonzini
2024-02-21 18:21 ` Greg Kroah-Hartman
2024-02-22 9:58 ` Paolo Bonzini
2024-02-22 12:55 ` Greg Kroah-Hartman
2024-02-22 13:31 ` Paolo Bonzini
2024-02-29 5:32 ` Greg Kroah-Hartman
2024-02-29 6:05 ` Greg Kroah-Hartman [this message]
2024-02-29 10:53 ` Paolo Bonzini
2024-02-29 20:05 ` Greg Kroah-Hartman
2024-02-22 6:01 ` Greg Kroah-Hartman
2024-02-22 12:35 ` REJECTED: " Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024022918-deepen-composed-c680@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.