From: syzbot <syzbot+65bb09a7208ce3d4a633@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
idosch@nvidia.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, petrm@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] kernel BUG in __nla_validate_parse
Date: Sat, 09 Mar 2024 21:44:03 -0800 [thread overview]
Message-ID: <0000000000009b68ac061347e975@google.com> (raw)
In-Reply-To: <00000000000088981b06133bc07b@google.com>
syzbot has bisected this issue to:
commit 2118f9390d83cf942de8b34faf3d35b54f9f4eee
Author: Petr Machata <petrm@nvidia.com>
Date: Wed Mar 6 12:49:15 2024 +0000
net: nexthop: Adjust netlink policy parsing for a new attribute
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13293b36180000
start commit: d7e14e534493 Merge tag 'mlx5-socket-direct-v3' of git://gi..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a93b36180000
console output: https://syzkaller.appspot.com/x/log.txt?x=17293b36180000
kernel config: https://syzkaller.appspot.com/x/.config?x=63afafeedf00ef8f
dashboard link: https://syzkaller.appspot.com/bug?extid=65bb09a7208ce3d4a633
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113a3399180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156404d6180000
Reported-by: syzbot+65bb09a7208ce3d4a633@syzkaller.appspotmail.com
Fixes: 2118f9390d83 ("net: nexthop: Adjust netlink policy parsing for a new attribute")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-03-10 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 15:13 [syzbot] [net?] kernel BUG in __nla_validate_parse syzbot
2024-03-09 15:25 ` Eric Dumazet
2024-03-09 18:40 ` Jakub Kicinski
2024-03-09 20:56 ` David Ahern
2024-03-09 16:02 ` syzbot
2024-03-10 5:44 ` syzbot [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=0000000000009b68ac061347e975@google.com \
--to=syzbot+65bb09a7208ce3d4a633@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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).