From: patchwork-bot+netdevbpf@kernel.org
To: luoxuanqiang <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, opurdila@ixiacom.com,
tim.bird@sony.com, luoxuanqiang@kylinos.cn,
stable@vger.kernel.org
Subject: Re: [PATCH net v1] llc: fix SAP refcount leak when creating incoming sockets
Date: Fri, 17 Jul 2026 11:20:07 +0000 [thread overview]
Message-ID: <178428720714.1673922.10721054190774288958.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260712130343.518797-1-xuanqiang.luo@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 12 Jul 2026 21:03:43 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> llc_sap_add_socket() takes a SAP reference for each socket added to a SAP,
> and llc_sap_remove_socket() releases it. llc_create_incoming_sock() takes
> an additional SAP reference after adding the child socket.
>
> This extra reference was balanced by an explicit llc_sap_put() in
> llc_ui_release() until commit 3100aa9d74db ("llc: fix SAP reference
> counting w.r.t. socket handling") removed that put. The corresponding hold
> in the accept path was left behind.
>
> [...]
Here is the summary with links:
- [net,v1] llc: fix SAP refcount leak when creating incoming sockets
https://git.kernel.org/netdev/net/c/2c72eb628634
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-07-17 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 13:03 [PATCH net v1] llc: fix SAP refcount leak when creating incoming sockets Xuanqiang Luo
2026-07-17 11:20 ` 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=178428720714.1673922.10721054190774288958.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tim.bird@sony.com \
--cc=xuanqiang.luo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox