From: lizetao <lizetao1@huawei.com>
To: Pavel Begunkov <asml.silence@gmail.com>, Jens Axboe <axboe@kernel.dk>
Cc: "io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Subject: RE: [PATCH] io_uring/io-wq: Fix a small time window for reading work->flags
Date: Wed, 15 Jan 2025 01:50:30 +0000 [thread overview]
Message-ID: <6d68ba2ae0d74895aec47379e94997cb@huawei.com> (raw)
In-Reply-To: <0993bb5e-debd-4513-9481-a7d93f8c3c25@gmail.com>
Hi,
> -----Original Message-----
> From: Pavel Begunkov <asml.silence@gmail.com>
> Sent: Wednesday, January 15, 2025 12:22 AM
> To: lizetao <lizetao1@huawei.com>; Jens Axboe <axboe@kernel.dk>
> Cc: io-uring@vger.kernel.org
> Subject: Re: [PATCH] io_uring/io-wq: Fix a small time window for reading work-
> >flags
>
> On 1/14/25 02:06, lizetao wrote:
> > There is a small time window that is modified by other tasks after
> > reading work->flags. It is changed to read before use, which is more
>
> Can you elaborate on what races with what? I don't immediately see any race
> here.
There is such a race context:
worker process
io_worker_handle_work: IORING_OP_ASYNC_CANCEL
io_wq_enqueue __io_wq_worker_cancel
work_flags = atomic_read(&work->flags); // no IO_WQ_WORK_CANCEL
atomic_or(IO_WQ_WORK_CANCEL, &work->flags);
if (work_flags & IO_WQ_WORK_CANCEL) // false
There seems to be a small time window here, resulting in the latest flags not being used.
>
> > in line with the semantics of atoms.
> > Fixes: 3474d1b93f89 ("io_uring/io-wq: make io_wq_work flags atomic")
> > Signed-off-by: Li Zetao <lizetao1@huawei.com>
> > ---
> > io_uring/io-wq.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/io_uring/io-wq.c b/io_uring/io-wq.c index
> > a38f36b68060..75096e77b1fe 100644
> > --- a/io_uring/io-wq.c
> > +++ b/io_uring/io-wq.c
> > @@ -932,7 +932,6 @@ static bool io_wq_work_match_item(struct
> io_wq_work *work, void *data)
> > void io_wq_enqueue(struct io_wq *wq, struct io_wq_work *work)
> > {
> > struct io_wq_acct *acct = io_work_get_acct(wq, work);
> > - unsigned int work_flags = atomic_read(&work->flags);
> > struct io_cb_cancel_data match = {
> > .fn = io_wq_work_match_item,
> > .data = work,
> > @@ -945,7 +944,7 @@ void io_wq_enqueue(struct io_wq *wq, struct
> io_wq_work *work)
> > * been marked as one that should not get executed, cancel it here.
> > */
> > if (test_bit(IO_WQ_BIT_EXIT, &wq->state) ||
> > - (work_flags & IO_WQ_WORK_CANCEL)) {
> > + (atomic_read(&work->flags) & IO_WQ_WORK_CANCEL)) {
> > io_run_cancel(work, wq);
> > return;
> > }
> > @@ -959,7 +958,7 @@ void io_wq_enqueue(struct io_wq *wq, struct
> io_wq_work *work)
> > do_create = !io_wq_activate_free_worker(wq, acct);
> > rcu_read_unlock();
> >
> > - if (do_create && ((work_flags & IO_WQ_WORK_CONCURRENT) ||
> > + if (do_create && ((atomic_read(&work->flags) &
> > +IO_WQ_WORK_CONCURRENT) ||
> > !atomic_read(&acct->nr_running))) {
> > bool did_create;
> >
>
> --
> Pavel Begunkov
---
Li Zetao
next prev parent reply other threads:[~2025-01-15 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:06 [PATCH] io_uring/io-wq: Fix a small time window for reading work->flags lizetao
2025-01-14 16:22 ` Pavel Begunkov
2025-01-15 1:50 ` lizetao [this message]
2025-01-15 12:55 ` 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 \
--in-reply-to=6d68ba2ae0d74895aec47379e94997cb@huawei.com \
--to=lizetao1@huawei.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.