From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+93f72b3885406bb09e0d@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in io_ring_exit_work
Date: Thu, 13 May 2021 22:15:32 +0100 [thread overview]
Message-ID: <eb659001-f646-95e7-2037-8615e116582f@gmail.com> (raw)
In-Reply-To: <0000000000002f920305c1c89a25@google.com>
On 5/8/21 3:50 AM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+93f72b3885406bb09e0d@syzkaller.appspotmail.com
May still be there but silent because of fixed buffers changes,
test with the old behaviour restored
#syz test: https://github.com/isilence/linux.git syz_test7
>
> Tested on:
>
> commit: 50b7b6f2 x86/process: setup io_threads more like normal us..
> git tree: git://git.kernel.dk/linux-block io_uring-5.13
> kernel config: https://syzkaller.appspot.com/x/.config?x=f81a36128b448b98
> dashboard link: https://syzkaller.appspot.com/bug?extid=93f72b3885406bb09e0d
> compiler:
>
> Note: testing is done by a robot and is best-effort only.
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-05-13 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 9:16 [syzbot] INFO: task hung in io_ring_exit_work syzbot
2021-04-05 19:11 ` Pavel Begunkov
2021-04-05 19:34 ` syzbot
2021-04-07 19:51 ` Pavel Begunkov
2021-04-07 23:52 ` syzbot
2021-04-08 0:38 ` Pavel Begunkov
2021-04-08 5:05 ` syzbot
2021-04-08 13:35 ` Pavel Begunkov
2021-04-08 13:57 ` syzbot
2021-04-08 13:58 ` Pavel Begunkov
2021-04-08 14:42 ` syzbot
2021-05-07 19:53 ` Pavel Begunkov
2021-05-08 2:50 ` syzbot
2021-05-13 21:15 ` Pavel Begunkov [this message]
2021-05-14 0:21 ` syzbot
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=eb659001-f646-95e7-2037-8615e116582f@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+93f72b3885406bb09e0d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).