From: James Bottomley <jejb@linux.ibm.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
DOV MURIK <Dov.Murik1@il.ibm.com>
Subject: Re: [PATCH] x86: fix q35 kernel measurements broken due to rng seeding
Date: Wed, 01 Feb 2023 10:24:06 -0500 [thread overview]
Message-ID: <2b8fc552e1dc3a14de404eeaff0819ec8da7de54.camel@linux.ibm.com> (raw)
In-Reply-To: <CAHmME9ouTTk1ONXm276CwunOpy=MAW1Q79x25kcQv=YJTZ88dQ@mail.gmail.com>
On Wed, 2023-02-01 at 10:10 -0500, Jason A. Donenfeld wrote:
> This is already fixed via the patch that MST just sent in his pull.
> So wait a few days for that to be merged and it'll be all set.
>
> No need for this patch here. Do not merge.
If it's not a secret, would it be too much trouble to point to the
branch so we can actually test it? It does seem that the biggest
problem this issue shows is that there wasn't wide enough configuration
testing done on the prior commits before they were merged.
James
next prev parent reply other threads:[~2023-02-01 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:57 [PATCH] x86: fix q35 kernel measurements broken due to rng seeding James Bottomley
2023-02-01 14:35 ` Daniel P. Berrangé
2023-02-01 14:56 ` James Bottomley
2023-02-01 15:12 ` Jason A. Donenfeld
2023-02-01 15:14 ` Daniel P. Berrangé
2023-02-01 15:10 ` Jason A. Donenfeld
2023-02-01 15:24 ` James Bottomley [this message]
2023-02-01 16:41 ` Dov Murik
2023-02-01 16:50 ` Peter Maydell
2023-02-01 19:35 ` James Bottomley
2023-02-01 17:51 ` Jason A. Donenfeld
2023-02-01 20:38 ` James Bottomley
2023-02-01 20:48 ` Jason A. Donenfeld
2023-02-02 14:38 ` James Bottomley
2023-02-02 15:03 ` H. Peter Anvin
2023-02-02 15:17 ` James Bottomley
2023-02-02 18:56 ` H. Peter Anvin
2023-02-02 19:02 ` H. Peter Anvin
2023-02-02 19:13 ` H. Peter Anvin
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=2b8fc552e1dc3a14de404eeaff0819ec8da7de54.camel@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=Dov.Murik1@il.ibm.com \
--cc=Jason@zx2c4.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).