From: Stefano Garzarella <sgarzare@redhat.com>
To: Raf Dickson <rafdog35@gmail.com>
Cc: pabeni@redhat.com, netdev@vger.kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
stefanha@redhat.com, bryan-bt.tan@broadcom.com,
vishnu.dasa@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
stable@vger.kernel.org
Subject: Re: [PATCH] vsock/vmci: fix sk_ack_backlog leak on failed handshake
Date: Thu, 4 Jun 2026 12:39:35 +0200 [thread overview]
Message-ID: <aiFT9FBrEW_fW3KW@sgarzare-redhat> (raw)
In-Reply-To: <20260601095646.180085-1-rafdog35@gmail.com>
On Mon, Jun 01, 2026 at 09:56:46AM +0000, Raf Dickson wrote:
>On Mon, Jun 1, 2026 at 9:26 AM Paolo Abeni wrote:
>> I'm wondering if sk_acceptq_removed() should be bounded in
>> vsock_remove_pending() ? (even if that change would probably be
>> net-next material).
>
>Agreed, that would prevent this class of bug entirely. Happy to prepare
>a follow-up patch for net-next once this fix lands, if that would be
>useful.
And maybe sk_acceptq_added() calls moved in vsock_add_pending().
That said I was wondering about other transports, but it seems both
virtio and hyperv have a simplier handshake that doesn't require the
pending list, since the socket is moved directly in the accept list.
BTW if you are going to sent a follow up, maybe another improvement
(unrelated so another patch) could be to use sk_acceptq_is_full()
instead of `sk->sk_ack_backlog >= sk->sk_max_ack_backlog`. Discovered
while comparing vmci with virtio.
Thanks,
Stefano
next prev parent reply other threads:[~2026-06-04 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 10:43 Raf Dickson
2026-06-01 9:25 ` Paolo Abeni
2026-06-01 9:56 ` Raf Dickson
2026-06-04 10:39 ` Stefano Garzarella [this message]
2026-06-04 10:40 ` Stefano Garzarella
2026-06-04 11:10 ` patchwork-bot+netdevbpf
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=aiFT9FBrEW_fW3KW@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafdog35@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.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
all inboxes | Powered by JetHome®