From: Pavel Begunkov <[email protected]>
To: Hao Xu <[email protected]>, Jens Axboe <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH 5.13] io_uring: don't set IORING_SQ_NEED_WAKEUP when sqthread is dying
Date: Tue, 27 Apr 2021 14:13:53 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/27/21 1:45 PM, Hao Xu wrote:
> we don't need to re-fork the sqthread over exec, so no need to set
> IORING_SQ_NEED_WAKEUP when sqthread is dying.
It forces users to call io_uring_enter() for it to return
-EOWNERDEAD. Consider that scenario with the ring given
away to some other task not in current group, e.g. via socket.
if (ctx->flags & IORING_SETUP_SQPOLL) {
io_cqring_overflow_flush(ctx, false);
ret = -EOWNERDEAD;
if (unlikely(ctx->sq_data->thread == NULL)) {
goto out;
}
...
}
btw, can use a comment
>
> Signed-off-by: Hao Xu <[email protected]>
> ---
> fs/io_uring.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 6b578c380e73..92dcd1c21516 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -6897,8 +6897,6 @@ static int io_sq_thread(void *data)
>
> io_uring_cancel_sqpoll(sqd);
> sqd->thread = NULL;
> - list_for_each_entry(ctx, &sqd->ctx_list, sqd_list)
> - io_ring_set_wakeup_flag(ctx);
> io_run_task_work();
> io_run_task_work_head(&sqd->park_task_work);
> mutex_unlock(&sqd->lock);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-04-27 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:45 [PATCH 5.13] io_uring: don't set IORING_SQ_NEED_WAKEUP when sqthread is dying Hao Xu
2021-04-27 13:13 ` Pavel Begunkov [this message]
2021-04-27 14:35 ` Hao Xu
2021-04-28 6:38 ` Hao Xu
2021-04-28 9:28 ` Pavel Begunkov
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] \
/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