From: "Theodore Ts'o" <tytso@mit.edu>
To: Paolo Bonzini <pbonzini@redhat.com>
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 08:34:54 -0600 [thread overview]
Message-ID: <20240229143454.GC272762@mit.edu> (raw)
In-Reply-To: <CABgObfZ+bMOac-yf2v6jD+s0-_RXACY3ApDknC2FnTmmgDXEug@mail.gmail.com>
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?
- Ted
next prev parent reply other threads:[~2024-02-29 14:35 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 ` CVE-2021-46978: KVM: nVMX: Always make an attempt to map eVMCS after migration 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 [this message]
2024-02-29 20:53 ` Paolo Bonzini
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=20240229143454.GC272762@mit.edu \
--to=tytso@mit.edu \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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