From: patchwork-bot+netdevbpf@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-hams@vger.kernel.org, jreuter@yaina.de,
ralf@linux-mips.org, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ax25: fix NPD and UAF bugs when detaching ax25 device
Date: Fri, 28 Jan 2022 15:10:11 +0000 [thread overview]
Message-ID: <164338261149.2420.16351407833253880236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1643343397.git.duoming@zju.edu.cn>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 28 Jan 2022 12:47:14 +0800 you wrote:
> There are NPD and UAF bugs when detaching ax25 device, we
> use lock and refcount to mitigate these bugs.
>
> Duoming Zhou (2):
> ax25: improve the incomplete fix to avoid UAF and NPD bugs
> ax25: add refcount in ax25_dev to avoid UAF bugs
>
> [...]
Here is the summary with links:
- [1/2] ax25: improve the incomplete fix to avoid UAF and NPD bugs
https://git.kernel.org/netdev/net/c/4e0f718daf97
- [2/2] ax25: add refcount in ax25_dev to avoid UAF bugs
https://git.kernel.org/netdev/net/c/d01ffb9eee4a
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:[~2022-01-28 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 4:47 Duoming Zhou
2022-01-28 4:47 ` [PATCH 1/2] ax25: improve the incomplete fix to avoid UAF and NPD bugs Duoming Zhou
2022-01-28 4:47 ` [PATCH 2/2] ax25: add refcount in ax25_dev to avoid UAF bugs Duoming Zhou
2022-01-31 13:22 ` Dan Carpenter
2022-02-01 14:53 ` 周多明
2022-01-31 17:37 ` Dan Carpenter
2022-02-01 6:26 ` 周多明
2022-01-28 15: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=164338261149.2420.16351407833253880236.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
/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
Powered by JetHome