From: syzbot <syzbot+343f75cdeea091340956@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org,
allison@lohutok.net, areber@redhat.com,
aubrey.li@linux.intel.com, avagin@gmail.com, bcrl@kvack.org,
christian@brauner.io, cyphar@cyphar.com, ebiederm@xmission.com,
gregkh@linuxfoundation.org, guro@fb.com, joel@joelfernandes.org,
keescook@chromium.org, linmiaohe@huawei.com, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mhocko@suse.com, mingo@kernel.org, oleg@redhat.com,
peterz@infradead.org, sargun@sargun.me,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in io_submit_one (3)
Date: Tue, 07 Apr 2020 02:31:02 -0700 [thread overview]
Message-ID: <000000000000cc522f05a2b00ad5@google.com> (raw)
In-Reply-To: <000000000000f59ac305a25cfa14@google.com>
syzbot has bisected this bug to:
commit 7bc3e6e55acf065500a24621f3b313e7e5998acf
Author: Eric W. Biederman <ebiederm@xmission.com>
Date: Thu Feb 20 00:22:26 2020 +0000
proc: Use a list of inodes to flush from proc
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12b3c9c7e00000
start commit: 7e634208 Merge tag 'acpi-5.7-rc1-2' of git://git.kernel.or..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=11b3c9c7e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16b3c9c7e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=12205d036cec317f
dashboard link: https://syzkaller.appspot.com/bug?extid=343f75cdeea091340956
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=105d592be00000
Reported-by: syzbot+343f75cdeea091340956@syzkaller.appspotmail.com
Fixes: 7bc3e6e55acf ("proc: Use a list of inodes to flush from proc")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-04-07 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 6:25 possible deadlock in io_submit_one (3) syzbot
2020-04-07 1:36 ` syzbot
2020-04-07 9:31 ` 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=000000000000cc522f05a2b00ad5@google.com \
--to=syzbot+343f75cdeea091340956@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=allison@lohutok.net \
--cc=areber@redhat.com \
--cc=aubrey.li@linux.intel.com \
--cc=avagin@gmail.com \
--cc=bcrl@kvack.org \
--cc=christian@brauner.io \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linmiaohe@huawei.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sargun@sargun.me \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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.