From: Markus Armbruster <armbru@redhat.com>
To: 晏龙龙 <yanlonglong@kylinos.cn>
Cc: qemu-devel <qemu-devel@nongnu.org>, John Snow <jsnow@redhat.com>
Subject: Re: 回复: 回复: Re: 回复: Re: [PATCH] hw/ide: resolve core crash caused by optical drive pop-up during virtual machine startup
Date: Thu, 02 Apr 2026 07:27:23 +0200 [thread overview]
Message-ID: <87v7eavsn8.fsf@pond.sub.org> (raw)
In-Reply-To: <2t5ely5d6lr9-2t5ka4g42q3q@nsmail8.2--kylin--1> ("晏龙龙"'s message of "Thu, 02 Apr 2026 09:17:30 +0800")
晏龙龙 <yanlonglong@kylinos.cn> writes:
> hi Maintainers :
>
> Do you have any further questions? I encountered this issue in a production environment,
> and resolving it in the repository resolved the problem ;If you do not agree, or may be
> change to :
>
> assert(blk_is_available(s->blk));
I'm not the maintainer, I'm just trying to help. You're not making it
easy, to be frank.
We don't apply patches just because they make a crash go away. We need
to understand both the bug and the patch.
Working backwards from just the patch to an understanding of the bug is
not practical. That's why I asked you for a reproducer and/or detailed
analysis of the bug. Your reply:
This bug occurs in VDI environments: When a virtual machine boots
up, the appearance of a CD drive may trigger a core crash. This
issue has been observed in our internal production environment, and
our internal testers have already conducted regression testing. You
may implement this method for testing purposes
This gives us precious little to work with.
What kind of virtual machine? How do you make a CD drive appear? Does
it crash always or only sometimes then? If sometimes, how often? Stack
backtrace of the crash? What did your regression testing find, if
anything? I could go on. I believe you're sitting on a wealth of
information. You can't expect us to spend our limited time to
rediscover what you already have, can you?
parent reply other threads:[~2026-04-02 5:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2t5ely5d6lr9-2t5ka4g42q3q@nsmail8.2--kylin--1>]
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=87v7eavsn8.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yanlonglong@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.