From: Pavel Begunkov <asml.silence@gmail.com>
To: Qian Cai <quic_qiancai@quicinc.com>, Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring: fix a GCC warning in wq_list_for_each()
Date: Wed, 27 Oct 2021 10:56:04 +0100 [thread overview]
Message-ID: <27d0d7bd-a5c3-27ca-03b3-ea3c5c363380@gmail.com> (raw)
In-Reply-To: <20211025145906.71955-1-quic_qiancai@quicinc.com>
On 10/25/21 15:59, Qian Cai wrote:
> fs/io_uring.c: In function '__io_submit_flush_completions':
> fs/io_uring.c:2367:33: warning: variable 'prev' set but not used
> [-Wunused-but-set-variable]
> 2367 | struct io_wq_work_node *node, *prev;
> | ^~~~
>
> Fixed it by open-coded the wq_list_for_each() without an unused previous
> node pointer.
That's intentional, the var is optimised out and it's better to
not hand code it (if possible).
> Fixes: 6f33b0bc4ea4 ("io_uring: use slist for completion batching")
> Signed-off-by: Qian Cai <quic_qiancai@quicinc.com>
> ---
> fs/io_uring.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 23641d9e0871..b8968bd43e3f 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2361,11 +2361,11 @@ static void io_free_batch_list(struct io_ring_ctx *ctx,
> static void __io_submit_flush_completions(struct io_ring_ctx *ctx)
> __must_hold(&ctx->uring_lock)
> {
> - struct io_wq_work_node *node, *prev;
> + struct io_wq_work_node *node;
> struct io_submit_state *state = &ctx->submit_state;
>
> spin_lock(&ctx->completion_lock);
> - wq_list_for_each(node, prev, &state->compl_reqs) {
> + for (node = state->compl_reqs.first; node; node = node->next) {
> struct io_kiocb *req = container_of(node, struct io_kiocb,
> comp_list);
>
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-10-27 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:59 Qian Cai
2021-10-27 9:56 ` Pavel Begunkov [this message]
2021-10-27 15:11 ` Qian Cai
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=27d0d7bd-a5c3-27ca-03b3-ea3c5c363380@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_qiancai@quicinc.com \
/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
all inboxes | Powered by JetHome®