From: syzbot <syzbot+08b7a2c58acdfa12c82d@syzkaller.appspotmail.com>
To: dave.stevenson@raspberrypi.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
unglinuxdriver@microchip.com, woojung.huh@microchip.com
Subject: Re: BUG: unable to handle kernel paging request in corrupted (2)
Date: Fri, 19 Jul 2019 04:56:00 -0700 [thread overview]
Message-ID: <000000000000fcdf6c058e076819@google.com> (raw)
In-Reply-To: <000000000000d8b010058e03aaf8@google.com>
syzbot has bisected this bug to:
commit 9343ac87f2a4e09bf6e27b5f31e72e9e3a82abff
Author: Dave Stevenson <dave.stevenson@raspberrypi.org>
Date: Mon Jun 25 14:07:15 2018 +0000
net: lan78xx: Use s/w csum check on VLANs without tag stripping
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=102feb84600000
start commit: 49d05fe2 ipv6: rt6_check should return NULL if 'from' is N..
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=122feb84600000
console output: https://syzkaller.appspot.com/x/log.txt?x=142feb84600000
kernel config: https://syzkaller.appspot.com/x/.config?x=87305c3ca9c25c70
dashboard link: https://syzkaller.appspot.com/bug?extid=08b7a2c58acdfa12c82d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143a78f4600000
Reported-by: syzbot+08b7a2c58acdfa12c82d@syzkaller.appspotmail.com
Fixes: 9343ac87f2a4 ("net: lan78xx: Use s/w csum check on VLANs without tag
stripping")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-07-19 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:28 BUG: unable to handle kernel paging request in corrupted (2) syzbot
2019-07-19 11:56 ` syzbot [this message]
2019-07-23 7:35 ` Dmitry Vyukov
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=000000000000fcdf6c058e076819@google.com \
--to=syzbot+08b7a2c58acdfa12c82d@syzkaller.appspotmail.com \
--cc=dave.stevenson@raspberrypi.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=unglinuxdriver@microchip.com \
--cc=woojung.huh@microchip.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).