From: Ricardo Dias <rdias@singlestore.com>
To: Eric Dumazet <edumazet@google.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] tcp: fix race condition when creating child sockets from syncookies
Date: Wed, 11 Nov 2020 18:05:55 +0000 [thread overview]
Message-ID: <20201111180555.GA1305169@rdias-suse-pc.lan> (raw)
In-Reply-To: <CANn89i+5PkUk5Lts+8jQR_AAhKUUDzODEAjBjRJpAs+BeKnKuw@mail.gmail.com>
On Wed, Nov 11, 2020 at 05:05:11PM +0100, Eric Dumazet wrote:
> On Wed, Nov 11, 2020 at 8:35 AM Ricardo Dias <rdias@singlestore.com> wrote:
>
> ...
>
> > + * If an existing socket already exists, it returns that socket
> > + * through the osk parameter.
>
>
> I think this deserves a third parameter, to avoid confusion.
Yes, I agree. It will make much clearer the semantics of this function.
> ...
>
> > + if (unlikely(!refcount_inc_not_zero(&esk->sk_refcnt)))
>
> Can you explain how this could happen ?
> Again, we own the lock here, finding a socket in ehash, with a zero
> refcount can not happen.
>
> Only a true rcu lookup could see a zero refcount.
Ah! Now I understand what you are saying. Indeed we just need to
increment the ref counter. We don't need to check if it's zero.
> ...
>
> > - inet_ehash_nolisten(sk, (struct sock *)tw);
> > + inet_ehash_nolisten(sk, (struct sock **)&tw);
>
> Why could not we 'find' a prior socket, and since you ignore the result,
> leave a refcount increment, and a socket leak ?
>
> Same remark for all callers.
>
> > }
> > if (tw)
>
> See the problem here ?
>
> If tw was initially NULL, then inet_ehash_nolisten() could have overwritten tw
> with another socket.
>
> Surely calling inet_twsk_bind_unhash() could be disastrous.
Yes, you're right.
I adapted this call to match the new signature assuming `tw` would never
be NULL. Shame on me for not noticing the `if (tw)` statement right
below :-).
I'll check each caller code, to make sure I'm not leaking the socket.
Thanks for your reviews. I'm learning more and more with each review
iteration.
prev parent reply other threads:[~2020-11-11 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 7:35 Ricardo Dias
2020-11-11 16:05 ` Eric Dumazet
2020-11-11 18:05 ` Ricardo Dias [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=20201111180555.GA1305169@rdias-suse-pc.lan \
--to=rdias@singlestore.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®