From: syzbot <syzbot+db1637662f412ac0d556@syzkaller.appspotmail.com>
To: benh@kernel.crashing.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
torvalds@linux-foundation.org
Subject: Re: general protection fault in kernfs_add_one
Date: Mon, 18 Nov 2019 22:27:01 -0800 [thread overview]
Message-ID: <000000000000e2ac670597ad2663@google.com> (raw)
In-Reply-To: <000000000000bf6bd30575fec528@google.com>
syzbot has bisected this bug to:
commit 726e41097920a73e4c7c33385dcc0debb1281e18
Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Tue Jul 10 00:29:10 2018 +0000
drivers: core: Remove glue dirs from sysfs earlier
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168e1012e00000
start commit: 5e335542 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=158e1012e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=118e1012e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9917ff4b798e1a1e
dashboard link: https://syzkaller.appspot.com/bug?extid=db1637662f412ac0d556
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a66c11400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1346c771400000
Reported-by: syzbot+db1637662f412ac0d556@syzkaller.appspotmail.com
Fixes: 726e41097920 ("drivers: core: Remove glue dirs from sysfs earlier")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-19 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 15:33 general protection fault in kernfs_add_one syzbot
2019-11-19 6:27 ` syzbot [this message]
2019-11-19 19:00 ` Linus Torvalds
2019-11-19 23:03 ` Marcel Holtmann
2019-11-20 4:03 ` Benjamin Herrenschmidt
2019-11-20 16:54 ` Linus Torvalds
2019-11-22 8:10 ` 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=000000000000e2ac670597ad2663@google.com \
--to=syzbot+db1637662f412ac0d556@syzkaller.appspotmail.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.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.