From: Guillaume Nault <gnault@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
netdev@vger.kernel.org, saeed@kernel.org, tparkin@katalix.com,
Cong Wang <cong.wang@bytedance.com>,
syzbot+52866e24647f9a23403f@syzkaller.appspotmail.com,
syzbot+94cc2a66fc228b23f360@syzkaller.appspotmail.com,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Jakub Sitnicki <jakub@cloudflare.com>
Subject: Re: [Patch net v3 2/2] l2tp: close all race conditions in l2tp_tunnel_register()
Date: Tue, 17 Jan 2023 11:57:02 +0100 [thread overview]
Message-ID: <Y8Z+/mH8Jv2Y3M6V@debian> (raw)
In-Reply-To: <CANn89iJ1FZvtyHgXC69YEVirg0B5moKM1eDLSU1skLQV0PNrGw@mail.gmail.com>
On Tue, Jan 17, 2023 at 09:10:20AM +0100, Eric Dumazet wrote:
> On Tue, Jan 17, 2023 at 9:08 AM Eric Dumazet <edumazet@google.com> wrote:
> > On Sat, Jan 14, 2023 at 4:01 AM Cong Wang <xiyou.wangcong@gmail.com> wrote:
> > > int l2tp_tunnel_create(int fd, int version, u32 tunnel_id, u32 peer_tunnel_id,
> > > struct l2tp_tunnel_cfg *cfg, struct l2tp_tunnel **tunnelp)
> > > {
> > > @@ -1482,21 +1480,16 @@ int l2tp_tunnel_register(struct l2tp_tunnel *tunnel, struct net *net,
> > > }
> > >
> > > sk = sock->sk;
> > > + lock_sock(sk);
> > > write_lock_bh(&sk->sk_callback_lock);
> > > ret = l2tp_validate_socket(sk, net, tunnel->encap);
> > > - if (ret < 0)
> > > + if (ret < 0) {
> >
> > I think we need to write_unlock_bh(&sk->sk_callback_lock)
> > before release_sock(), or risk lockdep reports.
> >
>
> Any objection if I propose :
>
> diff --git a/net/l2tp/l2tp_core.c b/net/l2tp/l2tp_core.c
> index b6554e32bb12ae7813cc06c01e4d1380af667375..03608d3ded4b83d1e59e064e482f54cffcdf5240
> 100644
> --- a/net/l2tp/l2tp_core.c
> +++ b/net/l2tp/l2tp_core.c
> @@ -1483,10 +1483,8 @@ int l2tp_tunnel_register(struct l2tp_tunnel
> *tunnel, struct net *net,
> lock_sock(sk);
> write_lock_bh(&sk->sk_callback_lock);
> ret = l2tp_validate_socket(sk, net, tunnel->encap);
> - if (ret < 0) {
> - release_sock(sk);
> + if (ret < 0)
> goto err_inval_sock;
> - }
> rcu_assign_sk_user_data(sk, tunnel);
> write_unlock_bh(&sk->sk_callback_lock);
>
> @@ -1523,6 +1521,7 @@ int l2tp_tunnel_register(struct l2tp_tunnel
> *tunnel, struct net *net,
>
> err_inval_sock:
> write_unlock_bh(&sk->sk_callback_lock);
> + release_sock(sk);
>
> if (tunnel->fd < 0)
> sock_release(sock);
Indeed, that looks more correct.
Thanks!
next prev parent reply other threads:[~2023-01-17 10:58 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 [this message]
2023-01-16 11:38 ` [Patch net v3 0/2] l2tp: fix " Tom Parkin
2023-01-16 13:50 ` patchwork-bot+netdevbpf
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=Y8Z+/mH8Jv2Y3M6V@debian \
--to=gnault@redhat.com \
--cc=cong.wang@bytedance.com \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=saeed@kernel.org \
--cc=syzbot+52866e24647f9a23403f@syzkaller.appspotmail.com \
--cc=syzbot+94cc2a66fc228b23f360@syzkaller.appspotmail.com \
--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).