From: Christoph Paasch <cpaasch@apple.com>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 1/5] tcp: Create list of TFO-contexts
Date: Mon, 17 Dec 2018 13:57:25 -0800 [thread overview]
Message-ID: <20181217215725.GZ41383@MacBook-Pro-19.local> (raw)
In-Reply-To: <CANn89iKHt4gr5C2S-t1386x4E_fv38KGk4QARPesAWXsThR4Fw@mail.gmail.com>
On 17/12/18 - 08:04:08, Eric Dumazet wrote:
> On Fri, Dec 14, 2018 at 2:40 PM Christoph Paasch <cpaasch@apple.com> wrote:
> >
>
> ...
>
> > int tcp_fastopen_reset_cipher(struct net *net, struct sock *sk,
> > void *key, unsigned int len)
> > {
> > @@ -96,13 +131,22 @@ error: kfree(ctx);
> > spin_lock(&net->ipv4.tcp_fastopen_ctx_lock);
> > if (sk) {
> > q = &inet_csk(sk)->icsk_accept_queue.fastopenq;
>
> > + rcu_assign_pointer(ctx->next, q->ctx);
> At this point, ctx is not yet visible, so you do not need a barrier yet
> ctx->next = q->ctx;
Thanks, I will change that.
>
>
> > + rcu_assign_pointer(q->ctx, ctx);
>
> Note that readers could see 3 contexts in the chain, instead of maximum two.
>
> This means that proc_tcp_fastopen_key() (your 3/5 change) would
> overflow an automatic array :
>
> while (ctxt) {
> memcpy(&key[i], ctxt->key, TCP_FASTOPEN_KEY_LENGTH);
> i += 4;
> ctxt = rcu_dereference(ctxt->next);
> }
Ouch! Thanks for spotting this.
If it's ok to have a brief moment of 3 contexts for the readers, I would
protect against overflows the readers.
> > +
> > octx = rcu_dereference_protected(q->ctx,
> > lockdep_is_held(&net->ipv4.tcp_fastopen_ctx_lock));
> > - rcu_assign_pointer(q->ctx, ctx);
> > +
> > + octx = tcp_fastopen_cut_keypool(octx, &net->ipv4.tcp_fastopen_ctx_lock);
> > } else {
> > + rcu_assign_pointer(ctx->next, net->ipv4.tcp_fastopen_ctx);
>
> same remark here.
Same, will change that.
Christoph
> > + rcu_assign_pointer(net->ipv4.tcp_fastopen_ctx, ctx);
> > +
> > octx = rcu_dereference_protected(net->ipv4.tcp_fastopen_ctx,
> > lockdep_is_held(&net->ipv4.tcp_fastopen_ctx_lock));
> > - rcu_assign_pointer(net->ipv4.tcp_fastopen_ctx, ctx);
> > +
> > + octx = tcp_fastopen_cut_keypool(octx,
> > + &net->ipv4.tcp_fastopen_ctx_lock);
> > }
> > spin_unlock(&net->ipv4.tcp_fastopen_ctx_lock);
> >
> > --
> > 2.16.2
> >
next prev parent reply other threads:[~2018-12-17 21:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 22:40 [PATCH net-next 0/5] tcp: Introduce a TFO key-pool for clean cookie-rotation Christoph Paasch
2018-12-14 22:40 ` [PATCH net-next 1/5] tcp: Create list of TFO-contexts Christoph Paasch
2018-12-17 6:31 ` Eric Dumazet
2018-12-17 15:49 ` Christoph Paasch
2018-12-17 16:07 ` Eric Dumazet
2018-12-17 16:04 ` Eric Dumazet
2018-12-17 21:57 ` Christoph Paasch [this message]
2018-12-17 22:01 ` Eric Dumazet
2018-12-17 22:50 ` Christoph Paasch
2018-12-14 22:40 ` [PATCH net-next 2/5] tcp: TFO: search for correct cookie and accept data Christoph Paasch
2018-12-17 6:30 ` Eric Dumazet
2018-12-17 22:59 ` Christoph Paasch
2018-12-14 22:40 ` [PATCH net-next 3/5] tcp: Print list of TFO-keys from proc Christoph Paasch
2018-12-17 6:32 ` Eric Dumazet
2018-12-17 16:52 ` Yuchung Cheng
2018-12-17 23:35 ` Christoph Paasch
2018-12-17 23:49 ` Yuchung Cheng
2018-12-14 22:40 ` [PATCH net-next 4/5] tcp: Allow getsockopt of listener's keypool Christoph Paasch
2018-12-14 22:40 ` [PATCH net-next 5/5] tcp: TFO - cleanup code duplication Christoph Paasch
2018-12-17 6:33 ` Eric Dumazet
2018-12-18 0:16 ` Christoph Paasch
2018-12-16 20:19 ` [PATCH net-next 0/5] tcp: Introduce a TFO key-pool for clean cookie-rotation David Miller
2018-12-17 5:54 ` Eric Dumazet
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=20181217215725.GZ41383@MacBook-Pro-19.local \
--to=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).