From: syzbot <syzbot+53c0b767f7ca0dc0c451@syzkaller.appspotmail.com>
To: adam.manzanares@wdc.com, avi@scylladb.com, bcrl@kvack.org,
darrick.wong@oracle.com, 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 userfaultfd_release
Date: Fri, 22 Mar 2019 00:14:00 -0700 [thread overview]
Message-ID: <0000000000005e71740584a999d1@google.com> (raw)
In-Reply-To: <000000000000700cdc057935aa71@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=1382985d200000
start commit: bfe4037e aio: implement IOCB_CMD_POLL
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1042985d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1782985d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=5c0a49d2b5210087
dashboard link: https://syzkaller.appspot.com/bug?extid=53c0b767f7ca0dc0c451
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1111f2eb400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e874f5400000
Reported-by: syzbot+53c0b767f7ca0dc0c451@syzkaller.appspotmail.com
Fixes: bfe4037e722e ("aio: implement IOCB_CMD_POLL")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-03-22 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 13:18 possible deadlock in userfaultfd_release syzbot
2019-03-22 7:14 ` syzbot [this message]
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=0000000000005e71740584a999d1@google.com \
--to=syzbot+53c0b767f7ca0dc0c451@syzkaller.appspotmail.com \
--cc=adam.manzanares@wdc.com \
--cc=avi@scylladb.com \
--cc=bcrl@kvack.org \
--cc=darrick.wong@oracle.com \
--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 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.