From: syzbot <syzbot+b70f2aabc707c69c9239@syzkaller.appspotmail.com>
To: chanho.min@lge.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mhocko@suse.com, oleg@redhat.com,
pavel@ucw.cz, rafael.j.wysocki@intel.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING: syz-executor still has locks held!
Date: Wed, 20 Mar 2019 05:24:00 -0700 [thread overview]
Message-ID: <0000000000004cdec6058485b2ce@google.com> (raw)
In-Reply-To: <0000000000000e4a41057b6c9792@google.com>
syzbot has bisected this bug to:
commit c22397888f1eed98cd59f0a88f2a5f6925f80e15
Author: Chanho Min <chanho.min@lge.com>
Date: Mon Nov 12 03:54:45 2018 +0000
exec: make de_thread() freezable
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ee6217200000
start commit: c2239788 exec: make de_thread() freezable
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=16ee6217200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12ee6217200000
kernel config: https://syzkaller.appspot.com/x/.config?x=73e2bc0cb6463446
dashboard link: https://syzkaller.appspot.com/bug?extid=b70f2aabc707c69c9239
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c9e26d400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14e1234d400000
Reported-by: syzbot+b70f2aabc707c69c9239@syzkaller.appspotmail.com
Fixes: c2239788 ("exec: make de_thread() freezable")
next prev parent reply other threads:[~2019-03-20 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 17:40 WARNING: syz-executor still has locks held! syzbot
2019-03-20 12:24 ` syzbot [this message]
2019-03-20 13:16 ` Michal Hocko
2019-03-20 13:24 ` Oleg Nesterov
2019-03-20 13:29 ` Michal Hocko
2019-03-20 15:00 ` Oleg Nesterov
2019-03-20 15:12 ` Michal Hocko
2019-03-20 17:30 ` Oleg Nesterov
2019-03-20 19:45 ` Michal Hocko
2019-03-20 20:32 ` Michal Hocko
2019-03-21 17:28 ` Oleg Nesterov
2019-03-22 10:36 ` Michal Hocko
2019-03-22 10:35 ` Pavel Machek
2019-03-20 13:18 ` Oleg Nesterov
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=0000000000004cdec6058485b2ce@google.com \
--to=syzbot+b70f2aabc707c69c9239@syzkaller.appspotmail.com \
--cc=chanho.min@lge.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=rafael.j.wysocki@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.