From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuho Choi <oss.patchbox@gmail.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
"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, 2 Nov 2026 11:33:36 -0500 [thread overview]
Message-ID: <20261102113328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAGG=RgDUFpDqtbws4YO4T8A3pS4Dr9twVqP9hSD3J_zP5Dc_mQ@mail.gmail.com>
On Mon, Oct 19, 2026 at 07:46:50PM -0400, Yuho Choi wrote:
> On Mon, 19 Oct 2026 at 09:05, David Hildenbrand (Arm) <david@kernel.org> wrote:
> >
> > Which kdump kernel exists that does not enable CONFIG_PROC_VMCORE?
> >
> > IOW, why should this be stable material?
>
> I tagged it because a9403425b3cf has been in releases since v6.14 and
> PROC_VMCORE can still be turned off with CRASH_DUMP enabled, so the
> -EBUSY path is reachable in a valid configuration. But as no practical
> kdump kernel disables it, I'll drop the Cc: stable in v2.
still did not get v2.
> > LGTM, but I am pretty sure it does not make any difference in practice?
>
> Right, nothing is queued on that path, so the device has nothing to
> access.
prev parent reply other threads:[~2026-11-02 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 2:35 Yuho Choi
2026-10-19 13:05 ` David Hildenbrand (Arm)
2026-10-19 23:46 ` Yuho Choi
2026-11-02 16:33 ` Michael S. Tsirkin [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=20261102113328-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®