From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sameo@linux.intel.com,
kuni1840@gmail.com, netdev@vger.kernel.org,
syzbot+f2d245f1d76bbfa50e4c@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().
Date: Tue, 27 Jan 2026 04:00:10 +0000 [thread overview]
Message-ID: <176948641060.677485.17878577493024735025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260125010214.1572439-1-kuniyu@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 25 Jan 2026 00:59:28 +0000 you wrote:
> syzbot reported various memory leaks related to NFC, struct
> nfc_llcp_sock, sk_buff, nfc_dev, etc. [0]
>
> The leading log hinted that nfc_llcp_send_ui_frame() failed
> to allocate skb due to sock_error(sk) being -ENXIO.
>
> ENXIO is set by nfc_llcp_socket_release() when struct
> nfc_llcp_local is destroyed by local_cleanup().
>
> [...]
Here is the summary with links:
- [v1,net] nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().
https://git.kernel.org/netdev/net/c/165c34fb6068
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-01-27 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 0:59 [PATCH v1 net] nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() Kuniyuki Iwashima
2026-01-26 17:24 ` Simon Horman
2026-01-27 4:00 ` 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=176948641060.677485.17878577493024735025.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=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sameo@linux.intel.com \
--cc=syzbot+f2d245f1d76bbfa50e4c@syzkaller.appspotmail.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 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.