From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], [email protected]
Cc: [email protected],
Xiaoguang Wang <[email protected]>
Subject: Re: [PATCH 1/1] io_uring: fix lazy work init
Date: Mon, 15 Jun 2020 16:59:44 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <a75c1537cc655cb766e8e2517e18f74e13d60f1b.1592228129.git.asml.silence@gmail.com>
On 15/06/2020 16:36, Pavel Begunkov wrote:
> Don't leave garbage in req.work before punting async on -EAGAIN
> in io_iopoll_queue().
oops, cc'ed a wrong person.
+Cc: Xiaoguang Wang
>
> [ 140.922099] general protection fault, probably for non-canonical
> address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI
> ...
> [ 140.922105] RIP: 0010:io_worker_handle_work+0x1db/0x480
> ...
> [ 140.922114] Call Trace:
> [ 140.922118] ? __next_timer_interrupt+0xe0/0xe0
> [ 140.922119] io_wqe_worker+0x2a9/0x360
> [ 140.922121] ? _raw_spin_unlock_irqrestore+0x24/0x40
> [ 140.922124] kthread+0x12c/0x170
> [ 140.922125] ? io_worker_handle_work+0x480/0x480
> [ 140.922126] ? kthread_park+0x90/0x90
> [ 140.922127] ret_from_fork+0x22/0x30
>
> Fixes: 7cdaf587de7c ("io_uring: avoid whole io_wq_work copy for requests
> completed inline")
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
> fs/io_uring.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 54addaba742d..410b2df16c71 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -1105,6 +1105,7 @@ static inline void io_prep_async_work(struct io_kiocb *req,
> req->work.flags |= IO_WQ_WORK_UNBOUND;
> }
>
> + io_req_init_async(req);
> io_req_work_grab_env(req, def);
>
> *link = io_prep_linked_timeout(req);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2020-06-15 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 13:36 [PATCH 1/1] io_uring: fix lazy work init Pavel Begunkov
2020-06-15 13:59 ` Pavel Begunkov [this message]
2020-06-15 14:38 ` Jens Axboe
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