From: David Ahern <dsahern@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, petrm@nvidia.com,
aroulin@nvidia.com
Subject: Re: [PATCH net 1/3] nexthop: Forbid FDB status change while nexthop is in a group
Date: Sun, 21 Sep 2025 09:35:32 -0600 [thread overview]
Message-ID: <d4b32b8e-568b-41e1-a9e7-5868d76066f7@kernel.org> (raw)
In-Reply-To: <20250921150824.149157-2-idosch@nvidia.com>
On 9/21/25 9:08 AM, Ido Schimmel wrote:
> The kernel forbids the creation of non-FDB nexthop groups with FDB
> nexthops:
>
> # ip nexthop add id 1 via 192.0.2.1 fdb
> # ip nexthop add id 2 group 1
> Error: Non FDB nexthop group cannot have fdb nexthops.
>
> And vice versa:
>
> # ip nexthop add id 3 via 192.0.2.2 dev dummy1
> # ip nexthop add id 4 group 3 fdb
> Error: FDB nexthop group can only have fdb nexthops.
>
> However, as long as no routes are pointing to a non-FDB nexthop group,
> the kernel allows changing the type of a nexthop from FDB to non-FDB and
> vice versa:
>
> # ip nexthop add id 5 via 192.0.2.2 dev dummy1
> # ip nexthop add id 6 group 5
> # ip nexthop replace id 5 via 192.0.2.2 fdb
> # echo $?
> 0
>
> This configuration is invalid and can result in a NPD [1] since FDB
> nexthops are not associated with a nexthop device:
>
> # ip route add 198.51.100.1/32 nhid 6
> # ping 198.51.100.1
>
> Fix by preventing nexthop FDB status change while the nexthop is in a
> group:
>
> # ip nexthop add id 7 via 192.0.2.2 dev dummy1
> # ip nexthop add id 8 group 7
> # ip nexthop replace id 7 via 192.0.2.2 fdb
> Error: Cannot change nexthop FDB status while in a group.
>
> [1]
> BUG: kernel NULL pointer dereference, address: 00000000000003c0
> [...]
> Oops: Oops: 0000 [#1] SMP
> CPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014
> RIP: 0010:fib_lookup_good_nhc+0x1e/0x80
> [...]
> Call Trace:
> <TASK>
> fib_table_lookup+0x541/0x650
> ip_route_output_key_hash_rcu+0x2ea/0x970
> ip_route_output_key_hash+0x55/0x80
> __ip4_datagram_connect+0x250/0x330
> udp_connect+0x2b/0x60
> __sys_connect+0x9c/0xd0
> __x64_sys_connect+0x18/0x20
> do_syscall_64+0xa4/0x2a0
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
>
> Fixes: 38428d68719c ("nexthop: support for fdb ecmp nexthops")
> Reported-by: syzbot+6596516dd2b635ba2350@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/netdev/68c9a4d2.050a0220.3c6139.0e63.GAE@google.com/
> Tested-by: syzbot+6596516dd2b635ba2350@syzkaller.appspotmail.com
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> net/ipv4/nexthop.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2025-09-21 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 15:08 [PATCH net 0/3] nexthop: Various fixes Ido Schimmel
2025-09-21 15:08 ` [PATCH net 1/3] nexthop: Forbid FDB status change while nexthop is in a group Ido Schimmel
2025-09-21 15:35 ` David Ahern [this message]
2025-09-21 15:08 ` [PATCH net 2/3] selftests: fib_nexthops: Fix creation of non-FDB nexthops Ido Schimmel
2025-09-21 15:36 ` David Ahern
2025-09-21 15:08 ` [PATCH net 3/3] selftests: fib_nexthops: Add test cases for FDB status change Ido Schimmel
2025-09-21 15:39 ` David Ahern
2025-09-24 0:20 ` [PATCH net 0/3] nexthop: Various fixes patchwork-bot+netdevbpf
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=d4b32b8e-568b-41e1-a9e7-5868d76066f7@kernel.org \
--to=dsahern@kernel.org \
--cc=aroulin@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.