From: syzbot <syzbot+a259a17220263c2d73fc@syzkaller.appspotmail.com>
To: andrew@lunn.ch, charmitro@posteo.net, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, kuniyu@amazon.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in nsim_fib_event_nb
Date: Fri, 30 May 2025 10:27:03 -0700 [thread overview]
Message-ID: <6839ea67.a00a0220.d8eae.000c.GAE@google.com> (raw)
In-Reply-To: <87r006nj7e.fsf@posteo.net>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for lo to become free. Usage count = 601
ref_tracker: lo@ffff888031d42610 has 600/600 users at
__netdev_tracker_alloc include/linux/netdevice.h:4330 [inline]
netdev_tracker_alloc include/linux/netdevice.h:4342 [inline]
netdev_get_by_index+0x79/0xb0 net/core/dev.c:1006
fib6_nh_init+0x1c4/0x2030 net/ipv6/route.c:3590
ip6_route_info_create_nh+0x139/0x870 net/ipv6/route.c:3866
ip6_route_mpath_info_create_nh net/ipv6/route.c:5429 [inline]
ip6_route_multipath_add net/ipv6/route.c:5544 [inline]
inet6_rtm_newroute+0x8ca/0x1d90 net/ipv6/route.c:5729
rtnetlink_rcv_msg+0x7cc/0xb70 net/core/rtnetlink.c:6955
netlink_rcv_skb+0x219/0x490 net/netlink/af_netlink.c:2534
netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline]
netlink_unicast+0x758/0x8d0 net/netlink/af_netlink.c:1339
netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1883
sock_sendmsg_nosec net/socket.c:712 [inline]
__sock_sendmsg+0x219/0x270 net/socket.c:727
____sys_sendmsg+0x505/0x830 net/socket.c:2566
___sys_sendmsg+0x21f/0x2a0 net/socket.c:2620
__sys_sendmsg net/socket.c:2652 [inline]
__do_sys_sendmsg net/socket.c:2657 [inline]
__se_sys_sendmsg net/socket.c:2655 [inline]
__x64_sys_sendmsg+0x19b/0x260 net/socket.c:2655
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Tested on:
commit: a5ecfdd9 ipv6: Fix ECMP validation for multipath routes
git tree: https://github.com/charmitro/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1151bff4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5a1787205a40c165
dashboard link: https://syzkaller.appspot.com/bug?extid=a259a17220263c2d73fc
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
Note: no patches were applied.
next prev parent reply other threads:[~2025-05-30 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 15:06 [syzbot] [net?] WARNING in nsim_fib_event_nb syzbot
2025-05-30 16:41 ` Charalampos Mitrodimas
2025-05-30 17:27 ` syzbot [this message]
2025-09-07 21:48 ` Forwarded: Re: " syzbot
[not found] <xb52gcH-aBgoaHrTJt9dVTtSOGhkj74ebC4qW0sGRe-uXFngQIjdHw2m34EjuC0uKR61elqaGsv5kGK6_XDffXSvueHkPVTFcRVLxNUeasM=@proton.me>
2025-09-07 22:17 ` syzbot
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=6839ea67.a00a0220.d8eae.000c.GAE@google.com \
--to=syzbot+a259a17220263c2d73fc@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=charmitro@posteo.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.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.