From: Greg KH <greg@kroah.com>
To: Luigi Leonardi <leonardi@redhat.com>
Cc: stable@vger.kernel.org, Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: Bunch of vsock patches for linux-stable
Date: Fri, 15 May 2026 17:13:45 +0200 [thread overview]
Message-ID: <2026051500-ashy-deplete-b04c@gregkh> (raw)
In-Reply-To: <CANo9s6mMchuAN-_9nWofGJq=mbRYP5X4ctc_5-Bis_-Z-zwnWA@mail.gmail.com>
On Fri, May 15, 2026 at 02:02:38PM +0200, Luigi Leonardi wrote:
> Hi stable maintainers,
>
> I realized that several vsock patches have not been backported to stable.
>
> They fixed various vsock bugs: incorrect buffer size clamping order,
> wrong length/offset and empty payloads in tap skbs, unbounded skb
> queue growth, and an accept queue counter leak.
>
> CCing the maintainer in case he has any objections.
>
> d114bfdc9b76 "vsock: fix buffer size clamping order"
>
> This applies cleanly to:
> 5.10.y
> 5.15.y
> 6.1.y
> 6.6.y
> 6.12.y
> 6.18.y
> 7.0.y
Now done.
> 5f344d809e01 "vsock/virtio: fix length and offset in tap skb for split packets"
> This applies cleanly to:
> 6.12.y
> 6.18.y
> 7.0.y
Now done.
> 3a3e3d90cbc7 "vsock/virtio: fix empty payload in tap skb for non-linear buffers"
>
> This patch requires "vsock/virtio: fix length and offset in tap skb
> for split packets" to be applied first.
> Then it applies cleanly to:
> 6.12.y
> 6.18.y
> 7.0.y
Now done.
> 059b7dbd20a6 "vsock/virtio: fix potential unbounded skb queue"
> This applies cleanly to:
> 6.12.y
> 6.18.y
> 7.0.y
Now done.
> 52bcb57a4e8a vsock/virtio: "fix accept queue count leak on transport mismatch"
> This applies cleanly to:
> 6.1.y
> 6.6.y
> 6.12.y
> 6.18.y
> 7.0.y
Now done, thanks!
greg k-h
prev parent reply other threads:[~2026-05-15 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:02 Bunch of vsock patches for linux-stable Luigi Leonardi
2026-05-15 15:13 ` Greg KH [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=2026051500-ashy-deplete-b04c@gregkh \
--to=greg@kroah.com \
--cc=leonardi@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable@vger.kernel.org \
/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