From: patchwork-bot+netdevbpf@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: krzysztof.kozlowski@linaro.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jeremy@jcline.org, horms@kernel.org, leitao@debian.org,
ilane@ti.com, linville@tuxdriver.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, khoroshilov@ispras.ru,
lvc-project@linuxtesting.org, stable@vger.kernel.org,
syzbot+6b7c68d9c21e4ee4251b@syzkaller.appspotmail.com
Subject: Re: [PATCH net] nfc: nci: free rx_data_reassembly skb on NCI device cleanup
Date: Mon, 29 Jan 2024 12:10:26 +0000 [thread overview]
Message-ID: <170653022632.12593.11211557853168091033.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240125095310.15738-1-pchelkin@ispras.ru>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 25 Jan 2024 12:53:09 +0300 you wrote:
> rx_data_reassembly skb is stored during NCI data exchange for processing
> fragmented packets. It is dropped only when the last fragment is processed
> or when an NTF packet with NCI_OP_RF_DEACTIVATE_NTF opcode is received.
> However, the NCI device may be deallocated before that which leads to skb
> leak.
>
> As by design the rx_data_reassembly skb is bound to the NCI device and
> nothing prevents the device to be freed before the skb is processed in
> some way and cleaned, free it on the NCI device cleanup.
>
> [...]
Here is the summary with links:
- [net] nfc: nci: free rx_data_reassembly skb on NCI device cleanup
https://git.kernel.org/netdev/net/c/bfb007aebe6b
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:[~2024-01-29 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 9:53 [PATCH net] nfc: nci: free rx_data_reassembly skb on NCI device cleanup Fedor Pchelkin
2024-01-29 12:10 ` 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=170653022632.12593.11211557853168091033.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ilane@ti.com \
--cc=jeremy@jcline.org \
--cc=khoroshilov@ispras.ru \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=stable@vger.kernel.org \
--cc=syzbot+6b7c68d9c21e4ee4251b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).