From: syzbot <syzbot+6c5d567447bfa30f78e2@syzkaller.appspotmail.com>
To: akinobu.mita@gmail.com, akpm@linux-foundation.org,
davem@davemloft.net, dvyukov@google.com,
linux-kernel@vger.kernel.org, mhocko@kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tejaswit@codeaurora.org, torvalds@linux-foundation.org
Subject: Re: BUG: unable to handle kernel paging request in slhc_free
Date: Sat, 16 Nov 2019 09:42:00 -0800 [thread overview]
Message-ID: <00000000000056b92d05977a3b19@google.com> (raw)
In-Reply-To: <000000000000675cea057e201cbb@google.com>
syzbot has bisected this bug to:
commit e41d58185f1444368873d4d7422f7664a68be61d
Author: Dmitry Vyukov <dvyukov@google.com>
Date: Wed Jul 12 21:34:35 2017 +0000
fault-inject: support systematic fault injection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144b8772e00000
start commit: 8fe28cb5 Linux 4.20
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=164b8772e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=124b8772e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d581260bae0899a
dashboard link: https://syzkaller.appspot.com/bug?extid=6c5d567447bfa30f78e2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136130fd400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1607c563400000
Reported-by: syzbot+6c5d567447bfa30f78e2@syzkaller.appspotmail.com
Fixes: e41d58185f14 ("fault-inject: support systematic fault injection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-16 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 2:41 BUG: unable to handle kernel paging request in slhc_free syzbot
2019-03-16 14:49 ` syzbot
2019-03-16 17:24 ` Linus Torvalds
2019-11-16 17:42 ` syzbot [this message]
2019-12-05 20:26 ` 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=00000000000056b92d05977a3b19@google.com \
--to=syzbot+6c5d567447bfa30f78e2@syzkaller.appspotmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tejaswit@codeaurora.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.