From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+6338dcebf269a590b668@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: INFO: task hung in io_uring_flush
Date: Mon, 10 Aug 2020 19:08:23 +0300 [thread overview]
Message-ID: <bff14407-8ad7-fdda-e5cf-0dabc1acbb0d@gmail.com> (raw)
In-Reply-To: <00000000000099566305ac881a16@google.com>
On 10/08/2020 19:04, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit f86cd20c9454847a524ddbdcdec32c0380ed7c9b
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Wed Jan 29 20:46:44 2020 +0000
>
> io_uring: fix linked command file table usage
There are several known problems with io_uring_cancel_files() including
races and hangs. I had some drafts and going to patch it in a week or so.
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16db4d3a900000
> start commit: 9420f1ce Merge tag 'pinctrl-v5.9-1' of git://git.kernel.or..
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=15db4d3a900000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11db4d3a900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=72cf85e4237850c8
> dashboard link: https://syzkaller.appspot.com/bug?extid=6338dcebf269a590b668
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141dde52900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b196aa900000
>
> Reported-by: syzbot+6338dcebf269a590b668@syzkaller.appspotmail.com
> Fixes: f86cd20c9454 ("io_uring: fix linked command file table usage")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
--
Pavel Begunkov
next prev parent reply other threads:[~2020-08-10 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 15:36 INFO: task hung in io_uring_flush syzbot
2020-08-10 16:04 ` syzbot
2020-08-10 16:08 ` Pavel Begunkov [this message]
2020-08-10 18:11 ` Jens Axboe
2020-09-17 1:42 ` syzbot
2020-11-11 11:21 ` Dmitry Vyukov
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=bff14407-8ad7-fdda-e5cf-0dabc1acbb0d@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6338dcebf269a590b668@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox