From: patchwork-bot+netdevbpf@kernel.org
To: Omid Ehtemam-Haghighi <omid.ehtemamhaghighi@menlosecurity.com>
Cc: netdev@vger.kernel.org, adrian.oliver@menlosecurity.com,
kernel@aoliver.ca, davem@davemloft.net, dsahern@gmail.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, idosch@idosch.org, kuniyu@amazon.com,
horms@kernel.org, oeh.kernel@gmail.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7] ipv6: Fix soft lockups in fib6_select_path under high next hop churn
Date: Mon, 11 Nov 2024 23:30:32 +0000 [thread overview]
Message-ID: <173136783228.10093.17478137468626631969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241106010236.1239299-1-omid.ehtemamhaghighi@menlosecurity.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 5 Nov 2024 17:02:36 -0800 you wrote:
> Soft lockups have been observed on a cluster of Linux-based edge routers
> located in a highly dynamic environment. Using the `bird` service, these
> routers continuously update BGP-advertised routes due to frequently
> changing nexthop destinations, while also managing significant IPv6
> traffic. The lockups occur during the traversal of the multipath
> circular linked-list in the `fib6_select_path` function, particularly
> while iterating through the siblings in the list. The issue typically
> arises when the nodes of the linked list are unexpectedly deleted
> concurrently on a different core—indicated by their 'next' and
> 'previous' elements pointing back to the node itself and their reference
> count dropping to zero. This results in an infinite loop, leading to a
> soft lockup that triggers a system panic via the watchdog timer.
>
> [...]
Here is the summary with links:
- [net-next,v7] ipv6: Fix soft lockups in fib6_select_path under high next hop churn
https://git.kernel.org/netdev/net-next/c/d9ccb18f83ea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-11 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:02 [PATCH net-next v7] ipv6: Fix soft lockups in fib6_select_path under high next hop churn Omid Ehtemam-Haghighi
2024-11-11 1:03 ` David Ahern
2024-11-11 23:30 ` patchwork-bot+netdevbpf [this message]
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=173136783228.10093.17478137468626631969.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adrian.oliver@menlosecurity.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=kernel@aoliver.ca \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oeh.kernel@gmail.com \
--cc=omid.ehtemamhaghighi@menlosecurity.com \
--cc=pabeni@redhat.com \
--cc=shuah@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).