From: Greg KH <gregkh@linuxfoundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: AVKrasnov@sberdevices.ru, edumazet@google.com,
eperezma@redhat.com, jasowang@redhat.com, kuba@kernel.org,
leonardi@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
virtualization@lists.linux.dev, xuanzhuo@linux.alibaba.com,
stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "vsock/virtio: fix potential unbounded skb queue" has been added to the 6.6-stable tree
Date: Fri, 15 May 2026 17:41:48 +0200 [thread overview]
Message-ID: <2026051526-banish-strife-6dba@gregkh> (raw)
In-Reply-To: <20260515113503-mutt-send-email-mst@kernel.org>
On Fri, May 15, 2026 at 11:36:12AM -0400, Michael S. Tsirkin wrote:
> On Fri, May 15, 2026 at 05:21:53PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > vsock/virtio: fix potential unbounded skb queue
> >
> > to the 6.6-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > vsock-virtio-fix-potential-unbounded-skb-queue.patch
> > and it can be found in the queue-6.6 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
>
> Yea I have some doubts. It fixes the DoS at the cost of losing
> messages. We are trying to fix that upstream now, maybe wait
> for that?
being bug compatible is good! :(
What's the status of that fix? Should it be reverted elsewhere?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-15 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:21 Patch "vsock/virtio: fix potential unbounded skb queue" has been added to the 6.6-stable tree gregkh
2026-05-15 15:36 ` Michael S. Tsirkin
2026-05-15 15:41 ` Greg KH [this message]
2026-05-15 15:47 ` Michael S. Tsirkin
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=2026051526-banish-strife-6dba@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=leonardi@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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.