From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Safonov <dima@arista.com>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ardb@kernel.org>,
Bob Gilligan <gilligan@arista.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Francesco Ruggeri <fruggeri@arista.com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Jason Baron <jbaron@akamai.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Salam Noureddine <noureddine@arista.com>,
Steven Rostedt <rostedt@goodmis.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH v4 3/5] net/tcp: Disable TCP-MD5 static key on tcp_md5sig_info destruction
Date: Mon, 21 Nov 2022 12:41:35 -0800 [thread overview]
Message-ID: <20221121124135.4015cc66@kernel.org> (raw)
In-Reply-To: <31efe48a-4c68-f17c-64ee-88d45f56c438@arista.com>
On Mon, 21 Nov 2022 20:31:38 +0000 Dmitry Safonov wrote:
> > Maybe it wouldn't be
> > the worst move to provide a sk_rcu_dereference() or rcu_dereference_sk()
> > or some such wrapper.
> >
> > More importantly tho - was the merging part for this patches discussed?
> > They don't apply to net-next.
>
> They apply over linux-next as there's a change [1] in
> linux-tip/locking/core on which the patches set based.
>
> Could the way forward be through linux-tip tree, or that might create
> net conflicts?
Dunno from memory, too much happens in these files :S
Could you cherry-pick [1] onto net-next and see if
git am --no-3way patches/*
goes thru cleanly? If so no objections for the patches to go via tip,
we're close enough to the merge window.
> I'll send v5 with the trivial change to rcu_dereference_protected()
> mentioned above.
next prev parent reply other threads:[~2022-11-21 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 21:19 [PATCH v4 0/5] net/tcp: Dynamically disable TCP-MD5 static key Dmitry Safonov
2022-11-15 21:19 ` [PATCH v4 1/5] jump_label: Prevent key->enabled int overflow Dmitry Safonov
2022-11-15 21:19 ` [PATCH v4 2/5] net/tcp: Separate tcp_md5sig_info allocation into tcp_md5sig_info_add() Dmitry Safonov
2022-11-15 21:19 ` [PATCH v4 3/5] net/tcp: Disable TCP-MD5 static key on tcp_md5sig_info destruction Dmitry Safonov
2022-11-19 3:18 ` Jakub Kicinski
2022-11-21 20:31 ` Dmitry Safonov
2022-11-21 20:41 ` Jakub Kicinski [this message]
2022-11-21 20:56 ` Dmitry Safonov
2022-11-22 3:53 ` Jakub Kicinski
2022-11-22 4:02 ` Eric Dumazet
2022-11-15 21:19 ` [PATCH v4 4/5] net/tcp: Do cleanup on tcp_md5_key_copy() failure Dmitry Safonov
2022-11-15 21:19 ` [PATCH v4 5/5] net/tcp: Separate initialization of twsk Dmitry Safonov
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=20221121124135.4015cc66@kernel.org \
--to=kuba@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=gilligan@arista.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).