From: Markus Armbruster <armbru@redhat.com>
To: Jie Song <mail@jiesong.me>
Cc: berrange@redhat.com, eblake@redhat.com,
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: Tue, 02 Dec 2025 13:07:04 +0100 [thread overview]
Message-ID: <87sedtt7dj.fsf@pond.sub.org> (raw)
In-Reply-To: <20251201130404.12083-1-mail@jiesong.me> (Jie Song's message of "Mon, 1 Dec 2025 21:04:03 +0800")
Jie Song <mail@jiesong.me> writes:
> 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.
This confirms Marc-André's "too late for 10.2" feeling.
I'll track this patch for 11.0. More review would be nice, but if we
can get it, I'll get the patch merged early in the development cycle.
Thank you!
next prev parent reply other threads:[~2025-12-02 12:07 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
2025-12-01 7:31 ` Marc-André Lureau
2025-12-01 13:04 ` Jie Song
2025-12-02 12:07 ` Markus Armbruster [this message]
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=87sedtt7dj.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.