From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: pbonzini@redhat.com, ebiggers@kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
ardb@kernel.org, kraxel@redhat.com, hpa@zytor.com, bp@alien8.de,
philmd@linaro.org
Subject: Re: [PATCH qemu v2] x86: don't let decompressed kernel image clobber setup_data
Date: Fri, 30 Dec 2022 22:59:46 +0100 [thread overview]
Message-ID: <Y69fUstLKNv/RLd7@zx2c4.com> (raw)
In-Reply-To: <20221230183819.604388-1-Jason@zx2c4.com>
On Fri, Dec 30, 2022 at 07:38:19PM +0100, Jason A. Donenfeld wrote:
> The microvm machine has a gross hack where it fiddles with fw_cfg data
> after the fact. So this hack is updated to account for this appending,
> by reserving some bytes.
This is a little derpy. I'll send a v3 in a second to clean this up.
next prev parent reply other threads:[~2022-12-30 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 18:38 [PATCH qemu v2] x86: don't let decompressed kernel image clobber setup_data Jason A. Donenfeld
2022-12-30 21:59 ` Jason A. Donenfeld [this message]
2022-12-30 22:07 ` [PATCH qemu v3] " Jason A. Donenfeld
2023-01-05 5:16 ` Eric Biggers
2023-01-10 12:10 ` Mathias Krause
2023-01-10 15:34 ` Jason A. Donenfeld
2023-01-10 17:50 ` Michael S. Tsirkin
2023-01-23 4:21 ` Eric Biggers
2023-01-23 12:12 ` Michael S. Tsirkin
2023-01-23 12:37 ` Jason A. Donenfeld
2023-01-28 11:15 ` Michael S. Tsirkin
2023-01-30 9:31 ` Daniel P. Berrangé
2023-01-23 8:26 ` Philippe Mathieu-Daudé
2023-02-08 17:45 ` Nathan Chancellor
2023-02-08 17:54 ` Jason A. Donenfeld
2023-02-08 18:09 ` Jason A. Donenfeld
2023-02-08 18:10 ` Michael S. Tsirkin
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=Y69fUstLKNv/RLd7@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=ebiggers@kernel.org \
--cc=hpa@zytor.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=x86@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 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).