From: Pavel Begunkov <[email protected]>
To: Palash Oswal <[email protected]>
Cc: Jens Axboe <[email protected]>,
[email protected], LKML <[email protected]>,
[email protected]
Subject: Re: INFO: task hung in io_uring_cancel_sqpoll
Date: Sun, 2 May 2021 11:33:59 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGyP=7czG1nmzpM5T784iBdApVL14hGoAfw-nhS=tNH5t9C79g@mail.gmail.com>
On 4/30/21 4:02 PM, Palash Oswal wrote:
> On Fri, Apr 30, 2021 at 8:03 PM Pavel Begunkov <[email protected]> wrote:
>>
>> On 4/30/21 3:21 PM, Palash Oswal wrote:
>>> On Thursday, March 18, 2021 at 9:40:21 PM UTC+5:30 syzbot wrote:
>>>>
>>>> Hello,
>>>>
>>>> syzbot found the following issue on:
>>>>
>>>> HEAD commit: 0d7588ab riscv: process: Fix no prototype for arch_dup_tas..
>>>> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
>>>> console output: https://syzkaller.appspot.com/x/log.txt?x=12dde5aed00000
>>>> kernel config: https://syzkaller.appspot.com/x/.config?x=81c0b708b31626cc
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=11bf59db879676f59e52
>>>> userspace arch: riscv64
>>>> CC: [[email protected] [email protected] [email protected] [email protected]]
>>>>
>>>> Unfortunately, I don't have any reproducer for this issue yet.
>>
>> There was so many fixes in 5.12 after this revision, including sqpoll
>> cancellation related... Can you try something more up-to-date? Like
>> released 5.12 or for-next
>>
>
> The reproducer works for 5.12.
Tried 5.12,
[ 245.467397] INFO: task iou-sqp-2018:2019 blocked for more than 122 seconds.
[ 245.467424] Call Trace:
[ 245.467432] __schedule+0x365/0x960
[ 245.467444] schedule+0x68/0xe0
[ 245.467450] io_uring_cancel_sqpoll+0xdb/0x110
[ 245.467461] ? wait_woken+0x80/0x80
[ 245.467472] io_sq_thread+0x1c6/0x6c0
[ 245.467482] ? wait_woken+0x80/0x80
[ 245.467491] ? finish_task_switch.isra.0+0xca/0x2e0
[ 245.467497] ? io_wq_submit_work+0x140/0x140
[ 245.467506] ret_from_fork+0x22/0x30
[ 245.467520] INFO: task iou-sqp-2052:2053 blocked for more than 122 seconds.
[ 245.467536] Call Trace:
[ 245.467539] __schedule+0x365/0x960
[ 245.467545] schedule+0x68/0xe0
[ 245.467550] io_uring_cancel_sqpoll+0xdb/0x110
[ 245.467559] ? wait_woken+0x80/0x80
[ 245.467568] io_sq_thread+0x1c6/0x6c0
[ 245.467577] ? wait_woken+0x80/0x80
[ 245.467586] ? finish_task_switch.isra.0+0xca/0x2e0
[ 245.467591] ? io_wq_submit_work+0x140/0x140
>
> I tested against the HEAD b1ef997bec4d5cf251bfb5e47f7b04afa49bcdfe
However, there is a bunch patches fixing sqpoll cancellations in
5.13, all are waiting for backporting. and for-next doesn't trigger
the issue for me.
Are you absolutely sure b1ef997bec4d5cf251bfb5e47f7b04afa49bcdfe
does hit it?
> commit on for-next tree
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/?h=for-next
> and the reproducer fails.
--
Pavel Begunkov
next prev parent reply other threads:[~2021-05-02 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
[not found] ` <[email protected]>
[not found] ` <[email protected]>
2021-04-30 14:21 ` INFO: task hung in io_uring_cancel_sqpoll Palash Oswal
2021-04-30 14:33 ` Pavel Begunkov
2021-04-30 15:02 ` Palash Oswal
2021-04-30 15:07 ` Pavel Begunkov
2021-04-30 15:11 ` Palash Oswal
2021-04-30 18:34 ` Pavel Begunkov
2021-04-30 18:34 ` syzbot
2021-04-30 21:04 ` Pavel Begunkov
2021-05-01 4:51 ` Palash Oswal
2021-05-01 7:39 ` Pavel Begunkov
2021-05-02 10:33 ` Pavel Begunkov [this message]
2021-05-02 15:01 ` Palash Oswal
2021-05-02 15:56 ` Pavel Begunkov
2021-05-02 22:12 ` Pavel Begunkov
2021-05-03 4:41 ` Palash Oswal
2021-05-03 10:45 ` Pavel Begunkov
[not found] ` <CAGyP=7eoSfh7z638PnP5UF4xVKcrG1jB_qmFo6uPZ7iWfu_2sQ@mail.gmail.com>
2021-05-13 21:28 ` Pavel Begunkov
2021-05-13 21:31 ` Pavel Begunkov
2021-05-15 7:44 ` Palash Oswal
2021-06-12 15:48 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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