From: Sasha Levin <sashal@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: cve@kernel.org, linux-cve-announce@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"
Date: Wed, 21 Feb 2024 09:35:54 -0500 [thread overview]
Message-ID: <ZdYKSkqRckOc5aRO@sashalap> (raw)
In-Reply-To: <bec7c1db-c13e-4b00-a968-4ae69539d7ac@redhat.com>
On Wed, Feb 21, 2024 at 02:15:12PM +0100, Paolo Bonzini wrote:
>>On 2/21/24 14:10, Sasha Levin wrote:
>>>On Wed, Feb 21, 2024 at 01:58:04PM +0100, Paolo Bonzini wrote:
>>>>On 2/21/24 13:34, Sasha Levin wrote:
>>>>>[snip]
>
>This conversation needs to be public.
I've cc'ed lkml.
>Please send your original answer as a reply to the message with
>"[resend]" in the subject, which has LKML in the Cc list, and we'll
>take it from there. I'm sorry about the confusion, but I didn't
>expect linux-cve-announce to be moderator-only, as that is a deviation
>from the common practice of vger.kernel.org.
You'll find that the convention for *-announce mailing list is that
they, as the name suggests, are used only for announces and are
moderated.
So for example, linux-kernel@ is the lkml we all know and love, while
linux-kernel-announce@ is an announcement-only mailing list used to
announce releases.
But thank you for pointing out this "deviation".
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-02-21 14:35 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 ` Sasha Levin [this message]
2024-02-21 15:02 ` CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" 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
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=ZdYKSkqRckOc5aRO@sashalap \
--to=sashal@kernel.org \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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.