From: Jie Song <mail@jiesong.me>
To: armbru@redhat.com
Cc: berrange@redhat.com, eblake@redhat.com, mail@jiesong.me,
marcandre.lureau@gmail.com, marcandre.lureau@redhat.com,
qemu-devel@nongnu.org, songjie_yewu@cmss.chinamobile.com
Subject: Re: [PATCH v4] monitor/qmp: cleanup SocketChardev listener sources early to avoid fd handling race
Date: Mon, 1 Dec 2025 21:04:03 +0800 [thread overview]
Message-ID: <20251201130404.12083-1-mail@jiesong.me> (raw)
In-Reply-To: <87ms424u8p.fsf@pond.sub.org>
Hi Markus,
> Jie Song, Marc-André, is this bug serious enough and the fix safe enough
> to still go into 10.2?
First, regarding the seriousness of this bug, although the probability of encountering
it in a production environment is relatively low, it has existed for quite some time.
Secondly, with regard to the safety of this fix, it has been verified successfully
in the test environment. However, it would be better if more people could help to
review it to further ensure its robustness.
>
> Jie Song <mail@jiesong.me> writes:
>
> > From: Jie Song <songjie_yewu@cmss.chinamobile.com>
> >
> > When starting a dummy QEMU process with virsh version, monitor_init_qmp()
> > enables IOThread monitoring of the QMP fd by default. However, a race
> > condition exists during the initialization phase: the IOThread only removes
> > the main thread's fd watch when it reaches qio_net_listener_set_client_func_full(),
> > which may be delayed under high system load.
> >
> > This creates a window between monitor_qmp_setup_handlers_bh() and
> > qio_net_listener_set_client_func_full() where both the main thread and
> > IOThread are simultaneously monitoring the same fd and processing events.
> > This race can cause either the main thread or the IOThread to hang and
> > become unresponsive.
> >
> > Fix this by proactively cleaning up the listener's IO sources in
> > monitor_init_qmp() before the IOThread initializes QMP monitoring,
> > ensuring exclusive fd ownership and eliminating the race condition.
> >
> > Signed-off-by: Jie Song <songjie_yewu@cmss.chinamobile.com>
> > Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Regards,
Jie Song
next prev parent reply other threads:[~2025-12-01 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 14:07 [PATCH v4] monitor/qmp: cleanup SocketChardev listener sources early to avoid fd handling race Jie Song
2025-12-01 6:00 ` Markus Armbruster
2025-12-01 7:31 ` Marc-André Lureau
2025-12-01 13:04 ` Jie Song [this message]
2025-12-02 12:07 ` Markus Armbruster
2025-12-02 13:03 ` Jie Song
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=20251201130404.12083-1-mail@jiesong.me \
--to=mail@jiesong.me \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=songjie_yewu@cmss.chinamobile.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;
as well as URLs for NNTP newsgroup(s).