From: patchwork-bot+netdevbpf@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-hams@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kuba@kernel.org,
davem@davemloft.net, ralf@linux-mips.org, jreuter@yaina.de,
eric.dumazet@gmail.com, dan.carpenter@oracle.com
Subject: Re: [PATCH V5 0/2] Fix refcount leak and NPD bugs in ax25
Date: Mon, 21 Mar 2022 11:00:10 +0000 [thread overview]
Message-ID: <164786041078.7161.8989814381753324978.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1647563511.git.duoming@zju.edu.cn>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 18 Mar 2022 08:54:03 +0800 you wrote:
> The first patch fixes refcount leak in ax25 that could cause
> ax25-ex-connected-session-now-listening-state-bug.
>
> The second patch fixes NPD bugs in ax25 timers.
>
> Duoming Zhou (2):
> ax25: Fix refcount leaks caused by ax25_cb_del()
> ax25: Fix NULL pointer dereferences in ax25 timers
>
> [...]
Here is the summary with links:
- [V5,1/2] ax25: Fix refcount leaks caused by ax25_cb_del()
https://git.kernel.org/netdev/net/c/9fd75b66b8f6
- [V6,2/2] ax25: Fix NULL pointer dereferences in ax25 timers
https://git.kernel.org/netdev/net/c/fc6d01ff9ef0
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-03-21 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 0:54 [PATCH V5 0/2] Fix refcount leak and NPD bugs in ax25 Duoming Zhou
2022-03-18 0:54 ` [PATCH V5 1/2] ax25: Fix refcount leaks caused by ax25_cb_del() Duoming Zhou
2022-03-18 0:54 ` [PATCH V6 2/2] ax25: Fix NULL pointer dereferences in ax25 timers Duoming Zhou
2022-03-21 11: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=164786041078.7161.8989814381753324978.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=eric.dumazet@gmail.com \
--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