All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org,  zhangckid@gmail.com,
	 lizhijian@fujitsu.com, jasowang@redhat.com,
	 arei.gonglei@huawei.com,  zhenwei.pi@linux.dev,
	pbonzini@redhat.com,  peterx@redhat.com,  philmd@linaro.org,
	berrange@redhat.com,  elena.ufimtseva@oracle.com,
	 jag.raman@oracle.com
Subject: Re: Several QOM objects crash on introspection
Date: Thu, 23 Apr 2026 06:55:10 +0200	[thread overview]
Message-ID: <87zf2us2c1.fsf@pond.sub.org> (raw)
In-Reply-To: <CAMxuvaxzwfYoguEijwHs4N5_iF8s8FLs853vse+mMaQA0ckQAQ@mail.gmail.com> ("Marc-André Lureau"'s message of "Thu, 23 Apr 2026 00:24:03 +0400")

Marc-André Lureau <marcandre.lureau@redhat.com> writes:

> Hi
>
> On Wed, Apr 22, 2026 at 6:16 PM Markus Armbruster <armbru@redhat.com> wrote:
>>
>> QMP command qom-list-properties crashes for the following object types:
>>
>>     colo-compare
>>     cryptodev-backend-lkcf
>>     memory-region-portio-list
>>     qemu-fixed-text-console
>>     qemu-graphic-console
>>     qio-net-listener
>>     x-remote-object
>>
>> Testing gap: tests/qtest/device-introspect-test.c guards against such
>> bugs in devices, but not non-device objects.
>
> Good catch, are you going to send a test for it?

I should; I wrote device-introspect-test.c.  I'll see what I can do.

> fwiw, I found also a critical in "filter-rewriter": (export
> G_DEBUG=fatal_criticals)

Reproduced.  Seems to be the only one.

Thanks!

[...]



  reply	other threads:[~2026-04-23  4:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 14:16 Several QOM objects crash on introspection Markus Armbruster
2026-04-22 20:24 ` Marc-André Lureau
2026-04-23  4:55   ` Markus Armbruster [this message]
2026-04-23 16:18     ` Jagannathan Raman
2026-04-23 17:31       ` Markus Armbruster
2026-04-23 18:36 ` Peter Xu

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=87zf2us2c1.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=berrange@redhat.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=jag.raman@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@fujitsu.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhangckid@gmail.com \
    --cc=zhenwei.pi@linux.dev \
    /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.