From: patchwork-bot+netdevbpf@kernel.org
To: Siddh Raman Pant <code@siddh.me>
Cc: krzysztof.kozlowski@linaro.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/2] nfc: Fix UAF during datagram sending caused by missing refcounting
Date: Mon, 25 Dec 2023 07:30:24 +0000 [thread overview]
Message-ID: <170348942430.19111.12016191837350222788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1702925869.git.code@siddh.me>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Dec 2023 23:19:42 +0530 you wrote:
> Changes in v7:
> - Stupidly reverted ordering in recv() too, fix that.
> - Remove redundant call to nfc_llcp_sock_free().
>
> Changes in v6:
> - Revert label introduction from v4, and thus also v5 entirely.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/2] nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local
https://git.kernel.org/netdev/net/c/c95f919567d6
- [net-next,v7,2/2] nfc: Do not send datagram if socket state isn't LLCP_BOUND
https://git.kernel.org/netdev/net/c/6ec0d7527c42
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:[~2023-12-25 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 17:49 [PATCH net-next v7 0/2] nfc: Fix UAF during datagram sending caused by missing refcounting Siddh Raman Pant
2023-12-19 17:49 ` [PATCH net-next v7 1/2] nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local Siddh Raman Pant
2023-12-23 19:04 ` Krzysztof Kozlowski
2023-12-19 17:49 ` [PATCH net-next v7 2/2] nfc: Do not send datagram if socket state isn't LLCP_BOUND Siddh Raman Pant
2023-12-25 7:30 ` 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=170348942430.19111.12016191837350222788.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=code@siddh.me \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.