From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, saeed@kernel.org, gnault@redhat.com,
tparkin@katalix.com, cong.wang@bytedance.com
Subject: Re: [Patch net v3 0/2] l2tp: fix race conditions in l2tp_tunnel_register()
Date: Mon, 16 Jan 2023 13:50:16 +0000 [thread overview]
Message-ID: <167387701646.13526.1819803351438649697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230114030137.672706-1-xiyou.wangcong@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 13 Jan 2023 19:01:35 -0800 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
>
> This patchset contains two patches, the first one is a preparation for
> the second one which is the actual fix. Please find more details in
> each patch description.
>
> I have ran the l2tp test (https://github.com/katalix/l2tp-ktest),
> all test cases are passed.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] l2tp: convert l2tp_tunnel_list to idr
https://git.kernel.org/netdev/net/c/c4d48a58f32c
- [net,v3,2/2] l2tp: close all race conditions in l2tp_tunnel_register()
https://git.kernel.org/netdev/net/c/0b2c59720e65
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-01-16 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 3:01 [Patch net v3 0/2] l2tp: fix race conditions in l2tp_tunnel_register() Cong Wang
2023-01-14 3:01 ` [Patch net v3 1/2] l2tp: convert l2tp_tunnel_list to idr Cong Wang
2023-01-16 11:07 ` Guillaume Nault
2023-01-14 3:01 ` [Patch net v3 2/2] l2tp: close all race conditions in l2tp_tunnel_register() Cong Wang
2023-01-16 11:08 ` Guillaume Nault
2023-01-17 8:08 ` Eric Dumazet
2023-01-17 8:10 ` Eric Dumazet
2023-01-17 10:57 ` Guillaume Nault
2023-01-16 11:38 ` [Patch net v3 0/2] l2tp: fix " Tom Parkin
2023-01-16 13:50 ` 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=167387701646.13526.1819803351438649697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=gnault@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=tparkin@katalix.com \
--cc=xiyou.wangcong@gmail.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).