From: patchwork-bot+netdevbpf@kernel.org
To: Shigeru Yoshida <syoshida@redhat.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
fmancera@suse.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+cb809def1baaac68ab92@syzkaller.appspotmail.com
Subject: Re: [PATCH net] ipv6: Fix ECMP sibling count mismatch when clearing RTF_ADDRCONF
Date: Thu, 05 Feb 2026 16:50:07 +0000 [thread overview]
Message-ID: <177031020757.485120.9003745936115169871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204095837.1285552-1-syoshida@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Feb 2026 18:58:37 +0900 you wrote:
> syzbot reported a kernel BUG in fib6_add_rt2node() when adding an IPv6
> route. [0]
>
> Commit f72514b3c569 ("ipv6: clear RA flags when adding a static
> route") introduced logic to clear RTF_ADDRCONF from existing routes
> when a static route with the same nexthop is added. However, this
> causes a problem when the existing route has a gateway.
>
> [...]
Here is the summary with links:
- [net] ipv6: Fix ECMP sibling count mismatch when clearing RTF_ADDRCONF
https://git.kernel.org/netdev/net/c/bbf4a17ad9ff
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:[~2026-02-05 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 9:58 [PATCH net] ipv6: Fix ECMP sibling count mismatch when clearing RTF_ADDRCONF Shigeru Yoshida
2026-02-04 12:59 ` Fernando Fernandez Mancera
2026-02-05 16:50 ` 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=177031020757.485120.9003745936115169871.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syoshida@redhat.com \
--cc=syzbot+cb809def1baaac68ab92@syzkaller.appspotmail.com \
/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