From: syzbot <syzbot+fc1da0f1a577d15b64fc@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, jamorris@linux.microsoft.com,
jmorris@namei.org, jslaby@suse.com, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp
Subject: Re: possible deadlock in console_trylock_spinning
Date: Tue, 25 Jun 2019 01:55:00 -0700 [thread overview]
Message-ID: <0000000000007b0e26058c2215d3@google.com> (raw)
In-Reply-To: <0000000000009ad686058bc12956@google.com>
syzbot has bisected this bug to:
commit e80b18599a39a625bc8b2e39ba3004a62f78805a
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Fri Apr 12 11:04:54 2019 +0000
tomoyo: Add a kernel config option for fuzzing testing.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=156e43cea00000
start commit: abf02e29 Merge tag 'pm-5.2-rc6' of git://git.kernel.org/pu..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=176e43cea00000
console output: https://syzkaller.appspot.com/x/log.txt?x=136e43cea00000
kernel config: https://syzkaller.appspot.com/x/.config?x=28ec3437a5394ee0
dashboard link: https://syzkaller.appspot.com/bug?extid=fc1da0f1a577d15b64fc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1357add6a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1611ac89a00000
Reported-by: syzbot+fc1da0f1a577d15b64fc@syzkaller.appspotmail.com
Fixes: e80b18599a39 ("tomoyo: Add a kernel config option for fuzzing
testing.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2019-06-25 8:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000009ad686058bc12956@google.com>]
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=0000000000007b0e26058c2215d3@google.com \
--to=syzbot+fc1da0f1a577d15b64fc@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jamorris@linux.microsoft.com \
--cc=jmorris@namei.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
/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).