From: patchwork-bot+netdevbpf@kernel.org
To: Ilia Gavrilov <Ilia.Gavrilov@infotecs.ru>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
georgezhang@vmware.com, dtor@vmware.com, acking@vmware.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH net v2] vsock: Fix memory leak in vmci_transport_recv_dgram_cb()
Date: Thu, 08 Oct 2026 18:50:13 +0000 [thread overview]
Message-ID: <179148541301.391001.8349992685770043645.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008144046.90853-1-Ilia.Gavrilov@infotecs.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Oct 2026 14:41:17 +0000 you wrote:
> During the closure of a datagram socket, the vmci_transport_recv_dgram_cb()
> function may be called, which will add the packets
> to the socket's backlog; then, after the receive queue is cleared,
> the __release_sock() function will move the packet back from the socket's
> backlog to the receive queue, which will lead to a memory leak.
>
> sock_close
> __sock_release
> __vsock_release
> // take ownership by user-space
> lock_sock_nested
> sock_set_flag(sk, SOCK_DEAD)
> vmci_transport_release
> vmci_dispatch_dgs
> vmci_datagram_invoke_guest_handler
> vmci_transport_recv_dgram_cb
> sk_receive_skb
> if (!sock_owned_by_user(sk))
> [...]
> (!) else if sk_add_backlog()
> [...]
> (!) skb_queue_purge(&sk->sk_receive_queue)
>
> [...]
Here is the summary with links:
- [net,v2] vsock: Fix memory leak in vmci_transport_recv_dgram_cb()
https://git.kernel.org/netdev/net/c/7c24a4e87e21
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-08 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 14:41 [PATCH net v2] vsock: Fix memory leak in vmci_transport_recv_dgram_cb() Ilia Gavrilov
2026-10-08 14:49 ` sashiko-bot
2026-10-08 18:50 ` patchwork-bot+netdevbpf [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=179148541301.391001.8349992685770043645.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ilia.Gavrilov@infotecs.ru \
--cc=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=dtor@vmware.com \
--cc=edumazet@kernel.org \
--cc=georgezhang@vmware.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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.