From: David Hildenbrand <david@redhat.com>
To: Gavin Shan <gshan@redhat.com>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
peter.maydell@linaro.org, philmd@linaro.org,
shan.gavin@gmail.com
Subject: Re: [PATCH v2] kvm: Fix crash due to access uninitialized kvm_state
Date: Mon, 31 Jul 2023 15:00:32 +0200 [thread overview]
Message-ID: <008f4ae2-c5bb-3570-3ec9-4ace4b5c4788@redhat.com> (raw)
In-Reply-To: <20230731125946.2038742-1-gshan@redhat.com>
On 31.07.23 14:59, Gavin Shan wrote:
> Runs into core dump on arm64 and the backtrace extracted from the
> core dump is shown as below. It's caused by accessing uninitialized
> @kvm_state in kvm_flush_coalesced_mmio_buffer() due to commit 176d073029
> ("hw/arm/virt: Use machine_memory_devices_init()"), where the machine's
> memory region is added earlier than before.
>
> main
> qemu_init
> configure_accelerators
> qemu_opts_foreach
> do_configure_accelerator
> accel_init_machine
> kvm_init
> virt_kvm_type
> virt_set_memmap
> machine_memory_devices_init
> memory_region_add_subregion
> memory_region_add_subregion_common
> memory_region_update_container_subregions
> memory_region_transaction_begin
> qemu_flush_coalesced_mmio_buffer
> kvm_flush_coalesced_mmio_buffer
>
> Fix it by bailing early in kvm_flush_coalesced_mmio_buffer() on the
> uninitialized @kvm_state. With this applied, no crash is observed on
> arm64.
>
> Fixes: 176d073029 ("hw/arm/virt: Use machine_memory_devices_init()")
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> v2: Bail early in kvm_flush_coalesced_mmio_buffer() on the uninitialized
> @kvm_state and improved changelog (David/Peter)
> ---
> accel/kvm/kvm-all.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index 373d876c05..7b3da8dc3a 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -2812,7 +2812,7 @@ void kvm_flush_coalesced_mmio_buffer(void)
> {
> KVMState *s = kvm_state;
>
> - if (s->coalesced_flush_in_progress) {
> + if (!s || s->coalesced_flush_in_progress) {
> return;
> }
>
Thanks Gavin!
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-07-31 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:59 [PATCH v2] kvm: Fix crash due to access uninitialized kvm_state Gavin Shan
2023-07-31 13:00 ` David Hildenbrand [this message]
2023-07-31 13:19 ` Peter Maydell
2023-07-31 13:55 ` Philippe Mathieu-Daudé
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=008f4ae2-c5bb-3570-3ec9-4ace4b5c4788@redhat.com \
--to=david@redhat.com \
--cc=gshan@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shan.gavin@gmail.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;
as well as URLs for NNTP newsgroup(s).