From: syzbot <syzbot+5ba06978f34abb058571@syzkaller.appspotmail.com>
To: ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, edumazet@google.com, hawk@kernel.org,
john.fastabend@gmail.com, kuba@kernel.org, leonro@nvidia.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] WARNING in dev_index_reserve
Date: Wed, 16 Aug 2023 21:19:42 -0700 [thread overview]
Message-ID: <000000000000a60932060316b8f1@google.com> (raw)
syzbot has bisected this issue to:
commit 956db0a13b47df7f3d6d624394e602e8bf9b057e
Author: Jakub Kicinski <kuba@kernel.org>
Date: Mon Aug 14 20:56:25 2023 +0000
net: warn about attempts to register negative ifindex
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f68f03a80000
start commit: 950fe35831af Merge branch 'ipv6-expired-routes'
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=140e8f03a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=100e8f03a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe63ad15dded26b6
dashboard link: https://syzkaller.appspot.com/bug?extid=5ba06978f34abb058571
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11be0117a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14950727a80000
Reported-by: syzbot+5ba06978f34abb058571@syzkaller.appspotmail.com
Fixes: 956db0a13b47 ("net: warn about attempts to register negative ifindex")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next reply other threads:[~2023-08-17 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 4:19 syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-16 19:07 [syzbot] [net?] WARNING in dev_index_reserve 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=000000000000a60932060316b8f1@google.com \
--to=syzbot+5ba06978f34abb058571@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.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 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).