From: Paolo Bonzini <pbonzini@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Greg KH <gregkh@kernel.org>,
cve@kernel.org, linux-kernel@vger.kernel.org,
KVM list <kvm@vger.kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: CVE-2021-46978: KVM: nVMX: Always make an attempt to map eVMCS after migration
Date: Thu, 29 Feb 2024 21:53:43 +0100 [thread overview]
Message-ID: <f25bc125-a013-4c43-b67d-09512786ae90@redhat.com> (raw)
In-Reply-To: <20240229143454.GC272762@mit.edu>
On 2/29/24 15:34, Theodore Ts'o wrote:
> On Thu, Feb 29, 2024 at 11:04:45AM +0100, Paolo Bonzini wrote:
>> Also, LKML does not get the initial announcement, which makes it a bit
>> more painful to find the full discussion on lore (you have to go
>> through a "no message with that id, maybe you mean this one from other
>> mailing lists" page, instead of having the whole thread in the same
>> place). A linux-cve mailing list with public posting, used for Cc and
>> Reply-to of the initial message, would solve this issue as well.
>
> I believe the url https://lore.kernel.org/all/<message-id> will get
> the whole thread, regardless of which mailing lists individual mail
> messages were sent to, does it not?
Yes, it does. That covers the web interface but it still leaves out
subscribers and people reading via NNTP.
That said, I'm not sure why people who look at CVEs for a living should
not have their own lighter-traffic mailing list, which was the main
reason to have a linux-cve mailing list.
Paolo
prev parent reply other threads:[~2024-02-29 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024022822-CVE-2021-46978-3516@gregkh>
2024-02-28 22:09 ` Paolo Bonzini
2024-02-29 5:21 ` Greg KH
2024-02-29 8:08 ` Vitaly Kuznetsov
2024-02-29 10:04 ` Paolo Bonzini
2024-02-29 14:34 ` Theodore Ts'o
2024-02-29 20:53 ` Paolo Bonzini [this message]
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=f25bc125-a013-4c43-b67d-09512786ae90@redhat.com \
--to=pbonzini@redhat.com \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vkuznets@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®