From: Sasha Levin <sashal@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
"Eric Dumazet" <edumazet@google.com>,
"Arseniy Krasnov" <AVKrasnov@sberdevices.ru>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev,
"Jakub Kicinski" <kuba@kernel.org>
Subject: Re: [PATCH 6.6 1008/1674] vsock/virtio: fix potential unbounded skb queue
Date: Mon, 19 Oct 2026 12:54:32 -0400 [thread overview]
Message-ID: <rc-reply-0004-be6cedb2b118@kernel.org> (raw)
In-Reply-To: <atYgJz85081YBziv@sgarzare-redhat>
On Mon, Oct 19, 2026 at 03:51:21PM +0200, Stefano Garzarella wrote:
> Be careful with this patch, this caused data loss. It's fixed upstream
> by commits:
[...]
> So if you want to backport this patch, I strongly recommend that you
> include these others as well in the same backport.
Thanks. I dropped 059b7dbd20a6 ("vsock/virtio: fix potential unbounded
skb queue") from the 6.6 queue, together with its two prerequisites that
were queued only for it:
- 0df7cd3c13e4 ("vsock/virtio/vhost: read data from non-linear skb")
- 45ca7e9f0730 ("vsock/virtio: fix `rx_bytes` accounting for stream
sockets")
It is dropped from 6.1 as well. If it comes back to 6.6, it will be with
the complete set of fixes.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-10-19 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261017160431.119607952@linuxfoundation.org>
2026-10-17 15:54 ` [PATCH 6.6 1008/1674] vsock/virtio: fix potential unbounded skb queue Greg Kroah-Hartman
2026-10-19 13:51 ` Stefano Garzarella
2026-10-19 16:54 ` Sasha Levin [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=rc-reply-0004-be6cedb2b118@kernel.org \
--to=sashal@kernel.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=patches@lists.linux.dev \
--cc=sgarzare@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox