From: syzbot <syzbot+3dcb532381f98c86aeb1@syzkaller.appspotmail.com>
To: benh@kernel.crashing.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, penguin-kernel@I-love.SAKURA.ne.jp,
rafael@kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org, torvalds@linux-foundation.org
Subject: Re: WARNING in kernfs_get
Date: Wed, 20 Nov 2019 00:17:01 -0800 [thread overview]
Message-ID: <0000000000001da6b60597c2ce91@google.com> (raw)
In-Reply-To: <000000000000f921ae05757f567c@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=17a101cee00000
start commit: 9a568276 Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=146101cee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=106101cee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=3dcb532381f98c86aeb1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12657f0a400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117728ae400000
Reported-by: syzbot+3dcb532381f98c86aeb1@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-20 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 7:31 WARNING in kernfs_get syzbot
2018-10-31 9:56 ` Tetsuo Handa
2019-11-20 8:17 ` syzbot [this message]
2019-11-20 8:29 ` Greg KH
2019-11-20 8:53 ` Dmitry Vyukov
2019-11-20 10:42 ` Tetsuo Handa
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=0000000000001da6b60597c2ce91@google.com \
--to=syzbot+3dcb532381f98c86aeb1@syzkaller.appspotmail.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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.