From: syzbot <syzbot+1de74b0794c40c8eb300@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
eric.dumazet@gmail.com, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
thinker.li@gmail.com
Subject: Re: [syzbot] [net?] general protection fault in modify_prefix_route
Date: Tue, 26 Nov 2024 11:31:07 -0800 [thread overview]
Message-ID: <674621fb.050a0220.21d33d.001e.GAE@google.com> (raw)
In-Reply-To: <67461f7f.050a0220.1286eb.0021.GAE@google.com>
syzbot has bisected this issue to:
commit 5eb902b8e7193cdcb33242af0a56502e6b5206e9
Author: Kui-Feng Lee <thinker.li@gmail.com>
Date: Thu Feb 8 22:06:51 2024 +0000
net/ipv6: Remove expired routes with a separated list of routes.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17a90dc0580000
start commit: 7eef7e306d3c Merge tag 'for-6.13/dm-changes' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14690dc0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10690dc0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c44a32edb32752c
dashboard link: https://syzkaller.appspot.com/bug?extid=1de74b0794c40c8eb300
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142375c0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=146f1530580000
Reported-by: syzbot+1de74b0794c40c8eb300@syzkaller.appspotmail.com
Fixes: 5eb902b8e719 ("net/ipv6: Remove expired routes with a separated list of routes.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-26 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 19:20 [syzbot] [net?] general protection fault in modify_prefix_route syzbot
2024-11-26 19:31 ` 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=674621fb.050a0220.21d33d.001e.GAE@google.com \
--to=syzbot+1de74b0794c40c8eb300@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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=syzkaller-bugs@googlegroups.com \
--cc=thinker.li@gmail.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