From: David Ahern <dsahern@kernel.org>
To: syzbot <syzbot+cb809def1baaac68ab92@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] kernel BUG in fib6_add_rt2node (2)
Date: Thu, 8 Jan 2026 17:56:41 -0700 [thread overview]
Message-ID: <e3ff455b-1c02-4f3b-9b57-1a9c7d5bd5fb@kernel.org> (raw)
In-Reply-To: <695d4d3a.050a0220.1c677c.0349.GAE@google.com>
On 1/6/26 10:58 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 1d528e794f3d Merge branch 'bpf-fix-bpf_d_path-helper-proto..
> git tree: bpf
> console output: https://syzkaller.appspot.com/x/log.txt?x=159c51c2580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9e5198eaf003f1d1
This config at
commit 59ba823e689f832f389ea6af6e7ae5842b3c860a (HEAD -> net-next,
net-next/main)
Merge: 76de4e1594b7 f2a3b12b305c
Author: Jakub Kicinski <kuba@kernel.org>
Date: Thu Jan 8 11:37:07 2026 -0800
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
> dashboard link: https://syzkaller.appspot.com/bug?extid=cb809def1baaac68ab92
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=139c51c2580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b2961a580000
and this reproducer does not show a problem for me.
prev parent reply other threads:[~2026-01-09 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 17:58 [syzbot] [net?] kernel BUG in fib6_add_rt2node (2) syzbot
2026-01-09 0:56 ` David Ahern [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=e3ff455b-1c02-4f3b-9b57-1a9c7d5bd5fb@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+cb809def1baaac68ab92@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox