From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 5.12] io_uring: fix io_sq_offload_create error handling
Date: Mon, 8 Mar 2021 11:51:30 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <fd95d5cfe8fd8dada11ed009678fc2304d5d3f64.1615224628.git.asml.silence@gmail.com>
On 3/8/21 10:30 AM, Pavel Begunkov wrote:
> Don't set IO_SQ_THREAD_SHOULD_STOP when io_sq_offload_create() has
> failed on io_uring_alloc_task_context() but leave everything to
> io_sq_thread_finish(), because currently io_sq_thread_finish()
> hangs on trying to park it. That's great it stalls there, because
> otherwise the following io_sq_thread_stop() would be skipped on
> IO_SQ_THREAD_SHOULD_STOP check and the sqo would race for sqd with
> freeing ctx.
>
> A simple error injection gives something like this.
>
> [ 245.463955] INFO: task sqpoll-test-hang:523 blocked for more than 122 seconds.
> [ 245.463983] Call Trace:
> [ 245.463990] __schedule+0x36b/0x950
> [ 245.464005] schedule+0x68/0xe0
> [ 245.464013] schedule_timeout+0x209/0x2a0
> [ 245.464032] wait_for_completion+0x8b/0xf0
> [ 245.464043] io_sq_thread_finish+0x44/0x1a0
> [ 245.464049] io_uring_setup+0x9ea/0xc80
> [ 245.464058] __x64_sys_io_uring_setup+0x16/0x20
> [ 245.464064] do_syscall_64+0x38/0x50
> [ 245.464073] entry_SYSCALL_64_after_hwframe+0x44/0xae
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-03-08 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 17:30 [PATCH 5.12] io_uring: fix io_sq_offload_create error handling Pavel Begunkov
2021-03-08 18:51 ` Jens Axboe [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 \
[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