[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221121124135.4015cc66@kernel.org>
Date: Mon, 21 Nov 2022 12:41:35 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Dmitry Safonov <dima@...sta.com>
Cc: linux-kernel@...r.kernel.org, David Ahern <dsahern@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Ard Biesheuvel <ardb@...nel.org>,
Bob Gilligan <gilligan@...sta.com>,
"David S. Miller" <davem@...emloft.net>,
Dmitry Safonov <0x7f454c46@...il.com>,
Francesco Ruggeri <fruggeri@...sta.com>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Jason Baron <jbaron@...mai.com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Salam Noureddine <noureddine@...sta.com>,
Steven Rostedt <rostedt@...dmis.org>, netdev@...r.kernel.org
Subject: Re: [PATCH v4 3/5] net/tcp: Disable TCP-MD5 static key on
tcp_md5sig_info destruction
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.
Powered by blists - more mailing lists