From: syzbot <syzbot+a3accb352f9c22041cfa@syzkaller.appspotmail.com>
To: adam.manzanares@wdc.com, avi@scylladb.com, bcrl@kvack.org,
darrick.wong@oracle.com, gregkh@linuxfoundation.org, hch@lst.de,
jmoyer@redhat.com, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in io_submit_one
Date: Mon, 11 Mar 2019 06:23:00 -0700 [thread overview]
Message-ID: <000000000000c2ebc60583d178e5@google.com> (raw)
In-Reply-To: <00000000000082477205811c029c@google.com>
syzbot has bisected this bug to:
commit bfe4037e722ec672c9dafd5730d9132afeeb76e9
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Jul 16 07:08:20 2018 +0000
aio: implement IOCB_CMD_POLL
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=108886bd200000
start commit: bfe4037e aio: implement IOCB_CMD_POLL
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=128886bd200000
console output: https://syzkaller.appspot.com/x/log.txt?x=148886bd200000
kernel config: https://syzkaller.appspot.com/x/.config?x=2e0064f906afee10
dashboard link: https://syzkaller.appspot.com/bug?extid=a3accb352f9c22041cfa
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156479f8c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128c75c4c00000
Reported-by: syzbot+a3accb352f9c22041cfa@syzkaller.appspotmail.com
Fixes: bfe4037e ("aio: implement IOCB_CMD_POLL")
next prev parent reply other threads:[~2019-03-11 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 2:03 possible deadlock in io_submit_one syzbot
2019-03-11 13:23 ` syzbot [this message]
2019-06-12 19:48 ` Eric Biggers
2019-06-27 7:50 ` [PATCH] userfaultfd: disable irqs for fault_pending and event locks Eric Biggers
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=000000000000c2ebc60583d178e5@google.com \
--to=syzbot+a3accb352f9c22041cfa@syzkaller.appspotmail.com \
--cc=adam.manzanares@wdc.com \
--cc=avi@scylladb.com \
--cc=bcrl@kvack.org \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).