[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3664acbd-6468-4ec0-946b-f6d8494e4a75@redhat.com>
Date: Tue, 5 Nov 2024 11:03:56 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: David Ahern <dsahern@...il.com>,
Omid Ehtemam-Haghighi <omid.ehtemamhaghighi@...losecurity.com>,
netdev@...r.kernel.org
Cc: adrian.oliver@...losecurity.com, Adrian Oliver <kernel@...iver.ca>,
"David S . Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Shuah Khan <shuah@...nel.org>, Ido Schimmel <idosch@...sch.org>,
Kuniyuki Iwashima <kuniyu@...zon.com>, Simon Horman <horms@...nel.org>,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net v6] ipv6: Fix soft lockups in fib6_select_path under
high next hop churn
On 10/31/24 15:10, David Ahern wrote:
> On 10/31/24 4:13 AM, Paolo Abeni wrote:
>> Given the issue is long-standing, and the fix is somewhat invasive, I
>> suggest steering this patch on net-next.
>
> FWIW, I think net-next is best.
Should I count the above as a formal ack? :-P
FWIW, I went through the patch as thoroughly as I could and LGTM, but it
does not apply (anymore?) to net-next.
@Omid: could you please rebase it on top of net-next and resend (with a
proper net-next tag)?
Thanks!
Paolo
Powered by blists - more mailing lists