[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220208170314.7fbd85c1@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 8 Feb 2022 17:03:14 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: netdev@...r.kernel.org, Kuniyuki Iwashima <kuniyu@...zon.co.jp>,
eric.dumazet@...il.com, davem@...emloft.net, dsahern@...nel.org,
efault@....de, tglx@...utronix.de, yoshfuji@...ux-ipv6.org,
Martin KaFai Lau <kafai@...com>
Subject: Re: [PATCH net v3] tcp: Don't acquire inet_listen_hashbucket::lock
with disabled BH.
On Tue, 8 Feb 2022 18:01:41 +0100 Sebastian Andrzej Siewior wrote:
> Reposted with fixes and net-tree as requested. Please keep in mind that
> this only effects the PREEMPT_RT preemption model and I'm posting this
> as part of the merging efforts. Therefore I didn't add the Fixes: tag
> and used net-next as I didn't expect any -stable backports (but then
> Greg sometimes backports RT-only patches since "it makes the life of
> some folks easier" as he puts it).
It says [PATCH net] in the the subject :S net-next makes sense.
Powered by blists - more mailing lists