From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Yuho Choi <oss.patchbox@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "Jason Wang" <jasowangio@gmail.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v1] virtio-mem: only mark the device ready in kdump mode with vmcore support
Date: Mon, 19 Oct 2026 15:05:43 +0200 [thread overview]
Message-ID: <25a35fa8-9540-4892-8375-1788e6795dfb@kernel.org> (raw)
In-Reply-To: <20261016023521.747447-1-oss.patchbox@gmail.com>
On 10/16/26 04:35, Yuho Choi wrote:
> virtio_mem_init_kdump() marks the device DRIVER_OK before it checks for
> CONFIG_PROC_VMCORE. Without vmcore support it then fails with -EBUSY,
> and virtio_mem_probe() deletes the virtqueue on that error path without
> resetting the device first, so the device is left believing the driver
> is ready while its queue points at memory that has been freed.
>
> Before commit a9403425b3cf ("virtio-mem: mark device ready before
> registering callbacks in kdump mode"), virtio_mem_probe() called
> virtio_device_ready() only after virtio_mem_init() had succeeded, so this
> path never exposed a ready device.
>
> Move virtio_device_ready() into the CONFIG_PROC_VMCORE branch, right
> before the vmcore callbacks that need it are registered, so the -EBUSY
> path never sets DRIVER_OK.
>
> Fixes: a9403425b3cf ("virtio-mem: mark device ready before registering callbacks in kdump mode")
> Cc: stable@vger.kernel.org
Which kdump kernel exists that does not enable CONFIG_PROC_VMCORE?
IOW, why should this be stable material?
> Signed-off-by: Yuho Choi <oss.patchbox@gmail.com>
> ---
> drivers/virtio/virtio_mem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/virtio_mem.c b/drivers/virtio/virtio_mem.c
> index e18dd736f2ec..b28d2da7d5b6 100644
> --- a/drivers/virtio/virtio_mem.c
> +++ b/drivers/virtio/virtio_mem.c
> @@ -2817,9 +2817,9 @@ static int virtio_mem_vmcore_get_device_ram(struct vmcore_cb *cb,
>
> static int virtio_mem_init_kdump(struct virtio_mem *vm)
> {
> +#ifdef CONFIG_PROC_VMCORE
> /* We must be prepared to receive a callback immediately. */
> virtio_device_ready(vm->vdev);
> -#ifdef CONFIG_PROC_VMCORE
> dev_info(&vm->vdev->dev, "memory hot(un)plug disabled in kdump kernel\n");
> vm->vmcore_cb.pfn_is_ram = virtio_mem_vmcore_pfn_is_ram;
> #ifdef CONFIG_PROC_VMCORE_DEVICE_RAM
LGTM, but I am pretty sure it does not make any difference in practice?
--
Cheers,
David
prev parent reply other threads:[~2026-10-19 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 2:35 Yuho Choi
2026-10-19 13:05 ` David Hildenbrand (Arm) [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=25a35fa8-9540-4892-8375-1788e6795dfb@kernel.org \
--to=david@kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=oss.patchbox@gmail.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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®