From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH v2 1/1] io_uring: cleanup files_update looping
Date: Tue, 26 Jan 2021 13:51:09 +0000 [thread overview]
Message-ID: <5998587a14bb4deff29beae622ff5a59a5bbedc4.1611668970.git.asml.silence@gmail.com> (raw)
Replace a while with a simple for loop, that looks way more natural, and
enables us to use "contiune" as indexes are no more updated by hand in
the end of the loop.
Signed-off-by: Pavel Begunkov <[email protected]>
---
v2: rebased onto for-5.12/io_uring
fs/io_uring.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 7a17c947e64b..783b3b7406ef 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -8011,9 +8011,8 @@ static int __io_sqe_files_update(struct io_ring_ctx *ctx,
return -ENOMEM;
init_fixed_file_ref_node(ctx, ref_node);
- done = 0;
fds = u64_to_user_ptr(up->data);
- while (nr_args) {
+ for (done = 0; done < nr_args; done++) {
struct fixed_rsrc_table *table;
unsigned index;
@@ -8022,7 +8021,7 @@ static int __io_sqe_files_update(struct io_ring_ctx *ctx,
err = -EFAULT;
break;
}
- i = array_index_nospec(up->offset, ctx->nr_user_files);
+ i = array_index_nospec(up->offset + done, ctx->nr_user_files);
table = &ctx->file_data->table[i >> IORING_FILE_TABLE_SHIFT];
index = i & IORING_FILE_TABLE_MASK;
if (table->files[index]) {
@@ -8060,9 +8059,6 @@ static int __io_sqe_files_update(struct io_ring_ctx *ctx,
break;
}
}
- nr_args--;
- done++;
- up->offset++;
}
if (needs_switch) {
--
2.24.0
next reply other threads:[~2021-01-26 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 13:51 Pavel Begunkov [this message]
2021-01-26 15:55 ` [PATCH v2 1/1] io_uring: cleanup files_update looping 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 \
--in-reply-to=5998587a14bb4deff29beae622ff5a59a5bbedc4.1611668970.git.asml.silence@gmail.com \
[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