From: Davide Caratti <dcaratti@redhat.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Boris Pismenny <borisp@mellanox.com>,
John Fastabend <john.fastabend@gmail.com>,
Dave Watson <davejwatson@fb.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] net/tls: use RCU protection on icsk->icsk_ulp_data
Date: Mon, 19 Aug 2019 15:23:31 +0200 [thread overview]
Message-ID: <b6741af18dace7eac9e2b6985de6bf6e33a6b852.camel@redhat.com> (raw)
In-Reply-To: <20190815143216.45f6da44@cakuba.netronome.com>
On Thu, 2019-08-15 at 14:32 -0700, Jakub Kicinski wrote:
> On Thu, 15 Aug 2019 18:00:42 +0200, Davide Caratti wrote:
> > From: Jakub Kicinski <jakub.kicinski@netronome.com>
> >
> > We need to make sure context does not get freed while diag
> > code is interrogating it. Free struct tls_context with
> > kfree_rcu().
> >
> > We add the __rcu annotation directly in icsk, and cast it
> > away in the datapath accessor. Presumably all ULPs will
> > do a similar thing.
> >
> > Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
hello Jakub,
> > @@ -251,14 +251,31 @@ static void tls_write_space(struct sock *sk)
> > ctx->sk_write_space(sk);
> > }
> >
> > -void tls_ctx_free(struct tls_context *ctx)
> > +/**
> > + * tls_ctx_free() - free TLS ULP context
> > + * @sk: socket to with @ctx is attached
> > + * @ctx: TLS context structure
> > + *
> > + * Free TLS context. If @sk is %NULL caller guarantees that the socket
> > + * to which @ctx was attached has no outstanding references.
> > + */
> > +void tls_ctx_free(struct sock *sk, struct tls_context *ctx)
> > {
> > + struct inet_connection_sock *icsk;
> > +
> > if (!ctx)
> > return;
> >
> > memzero_explicit(&ctx->crypto_send, sizeof(ctx->crypto_send));
> > memzero_explicit(&ctx->crypto_recv, sizeof(ctx->crypto_recv));
> > - kfree(ctx);
> > +
> > + if (sk) {
> > + icsk = inet_csk(sk);
> > + rcu_assign_pointer(icsk->icsk_ulp_data, NULL);
>
> Now that we kind of want to set the icsk_ulp_data to NULL under the
> callback_lock I think we should let the callers do it.
Ok, I will fix this in series v2.
> >
> > @@ -649,8 +666,8 @@ static void tls_hw_sk_destruct(struct sock *sk)
> >
> > ctx->sk_destruct(sk);
> > /* Free ctx */
> > - tls_ctx_free(ctx);
> > - icsk->icsk_ulp_data = NULL;
> > + tls_ctx_free(sk, ctx);
> > + rcu_assign_pointer(icsk->icsk_ulp_data, NULL);
>
> Let's reorder the assignment before the free.
Ok, I will fix this in series v2.
thanks!
--
davide
next prev parent reply other threads:[~2019-08-19 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 16:00 [PATCH net-next 0/3] net: tls: add socket diag Davide Caratti
2019-08-15 16:00 ` [PATCH net-next 1/3] net/tls: use RCU protection on icsk->icsk_ulp_data Davide Caratti
2019-08-15 21:32 ` Jakub Kicinski
2019-08-19 13:23 ` Davide Caratti [this message]
2019-08-15 16:00 ` [PATCH net-next 2/3] tcp: ulp: add functions to dump ulp-specific information Davide Caratti
2019-08-15 18:46 ` Eric Dumazet
2019-08-15 21:38 ` Jakub Kicinski
2019-08-19 13:32 ` Davide Caratti
2019-08-19 20:40 ` Jakub Kicinski
2019-08-15 16:00 ` [PATCH net-next 3/3] net: tls: export protocol version, cipher, tx_conf/rx_conf to socket diag Davide Caratti
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=b6741af18dace7eac9e2b6985de6bf6e33a6b852.camel@redhat.com \
--to=dcaratti@redhat.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).