qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, "Grant Millar | Cylo" <rid@cylo.io>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v2 0/3] io: fix crash in VNC websock server when client quits early
Date: Mon, 27 Oct 2025 10:18:42 +0000	[thread overview]
Message-ID: <aP9HAtXK1HJlKzbO@redhat.com> (raw)
In-Reply-To: <6f06c770-d66a-4520-8646-30b30c990235@tls.msk.ru>

On Sun, Oct 26, 2025 at 11:02:48AM +0300, Michael Tokarev wrote:
> On 10/3/25 18:02, Daniel P. Berrangé wrote:
> > See patch 3 for the description of the problem and reproducer
> > 
> > Changes in v2:
> > 
> >   - Improve finalizer robustness of TLS source
> >   - Keep cleanup in finalizer of websock, just augment
> >     it in the close method
> >   - Fix resetting of hs_ioc_tag value when callback
> >     is complete
> >   - Add CVE assignemnt in 3rd patch
> > 
> > Daniel P. Berrangé (3):
> >    io: release active GSource in TLS channel finalizer
> >    io: move websock resource release to close method
> >    io: fix use after free in websocket handshake code
> > 
> >   include/io/channel-websock.h |  3 ++-
> >   io/channel-tls.c             | 10 ++++++++++
> >   io/channel-websock.c         | 33 ++++++++++++++++++++++++++-------
> >   3 files changed, 38 insertions(+), 8 deletions(-)
> 
> Hi Daniel!
> 
> Is this patchset not supposed to go to the stable qemu series?
> I think it should?

Yes, it is applicable to all active stable branches - the bug has been
present since 2.6.0 AFAICT.

I've just sent a pull request for master

  https://lists.nongnu.org/archive/html/qemu-devel/2025-10/msg06571.html

these three websock related patches will probably cherry-pick without
trouble.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2025-10-27 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 15:02 [PATCH v2 0/3] io: fix crash in VNC websock server when client quits early Daniel P. Berrangé
2025-10-03 15:02 ` [PATCH v2 1/3] io: release active GSource in TLS channel finalizer Daniel P. Berrangé
2025-10-16 14:13   ` Eric Blake
2025-10-03 15:02 ` [PATCH v2 2/3] io: move websock resource release to close method Daniel P. Berrangé
2025-10-16 14:15   ` Eric Blake
2025-10-03 15:02 ` [PATCH v2 3/3] io: fix use after free in websocket handshake code Daniel P. Berrangé
2025-10-16 14:19   ` Eric Blake
2025-10-26  8:02 ` [PATCH v2 0/3] io: fix crash in VNC websock server when client quits early Michael Tokarev
2025-10-27 10:18   ` Daniel P. Berrangé [this message]

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=aP9HAtXK1HJlKzbO@redhat.com \
    --to=berrange@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=rid@cylo.io \
    /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).