From: Markus Armbruster <armbru@redhat.com>
To: Jie Song <mail@jiesong.me>
Cc: marcandre.lureau@gmail.com, eblake@redhat.com,
berrange@redhat.com, qemu-devel@nongnu.org,
songjie_yewu@cmss.chinamobile.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v4] monitor/qmp: cleanup SocketChardev listener sources early to avoid fd handling race
Date: Mon, 01 Dec 2025 07:00:06 +0100 [thread overview]
Message-ID: <87ms424u8p.fsf@pond.sub.org> (raw)
In-Reply-To: <20251125140706.114197-1-mail@jiesong.me> (Jie Song's message of "Tue, 25 Nov 2025 22:07:06 +0800")
Jie Song, Marc-André, is this bug serious enough and the fix safe enough
to still go into 10.2?
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>
next prev parent reply other threads:[~2025-12-01 6:01 UTC|newest]
Thread overview: 8+ 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 [this message]
2025-12-01 7:31 ` Marc-André Lureau
2025-12-01 13:04 ` Jie Song
2025-12-02 12:07 ` Markus Armbruster
2025-12-02 13:03 ` Jie Song
2026-01-08 14:51 ` Michael Tokarev
2026-01-14 13:18 ` 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=87ms424u8p.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=mail@jiesong.me \
--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 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.