All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: yanlonglong <yanlonglong@kylinos.cn>
Cc: qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH] hw/ide: resolve core crash caused by optical drive pop-up during virtual machine startup
Date: Fri, 20 Mar 2026 07:57:51 +0100	[thread overview]
Message-ID: <87341vkmxc.fsf@pond.sub.org> (raw)
In-Reply-To: <20260320020724.8714-1-yanlonglong@kylinos.cn> (yanlonglong@kylinos.cn's message of "Fri, 20 Mar 2026 10:07:24 +0800")

Reproducer?

Is this a regression?

yanlonglong <yanlonglong@kylinos.cn> writes:

> Signed-off-by: yanlonglong <yanlonglong@kylinos.cn>
> ---
>  hw/ide/atapi.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/hw/ide/atapi.c b/hw/ide/atapi.c
> index a42b748521..d14feed45b 100644
> --- a/hw/ide/atapi.c
> +++ b/hw/ide/atapi.c
> @@ -153,6 +153,11 @@ static void cd_read_sector_cb(void *opaque, int ret)
>  static int cd_read_sector(IDEState *s)
>  {
>      void *buf;
> +    
> +    //resolve core crash caused by optical drive pop-up during virtual machine startup

docs/devel/style.rst:

    We use traditional C-style /``*`` ``*``/ comments and avoid // comments.

> +    if (!blk_is_available(s->blk)) {
> +        return -ENOMEDIUM;
> +    }
>  
>      if (s->cd_sector_size != 2048 && s->cd_sector_size != 2352) {
>          block_acct_invalid(blk_get_stats(s->blk), BLOCK_ACCT_READ);



  reply	other threads:[~2026-03-20  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  2:07 [PATCH] hw/ide: resolve core crash caused by optical drive pop-up during virtual machine startup yanlonglong
2026-03-20  6:57 ` Markus Armbruster [this message]
2026-03-20  7:08 ` 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=87341vkmxc.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.