From: Dan Carpenter <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected]
Subject: [bug report] io_uring: add support for fixed wait regions
Date: Wed, 30 Oct 2024 14:40:45 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
Hello Jens Axboe,
Commit 4b926ab18279 ("io_uring: add support for fixed wait regions")
from Oct 22, 2024 (linux-next), leads to the following Smatch static
checker warning:
io_uring/register.c:616 io_register_cqwait_reg()
warn: was expecting a 64 bit value instead of '~(~(((1) << 12) - 1))'
io_uring/register.c
594 static int io_register_cqwait_reg(struct io_ring_ctx *ctx, void __user *uarg)
595 {
596 struct io_uring_cqwait_reg_arg arg;
597 struct io_uring_reg_wait *reg;
598 struct page **pages;
599 unsigned long len;
600 int nr_pages, poff;
601 int ret;
602
603 if (ctx->cq_wait_page || ctx->cq_wait_arg)
604 return -EBUSY;
605 if (copy_from_user(&arg, uarg, sizeof(arg)))
606 return -EFAULT;
607 if (!arg.nr_entries || arg.flags)
608 return -EINVAL;
609 if (arg.struct_size != sizeof(*reg))
610 return -EINVAL;
611 if (check_mul_overflow(arg.struct_size, arg.nr_entries, &len))
612 return -EOVERFLOW;
613 if (len > PAGE_SIZE)
614 return -EINVAL;
615 /* offset + len must fit within a page, and must be reg_wait aligned */
--> 616 poff = arg.user_addr & ~PAGE_MASK;
This is a harmless thing, but on 32 bit systems you can put whatever you want in
the high 32 bits of arg.user_addr and it won't affect anything.
617 if (len + poff > PAGE_SIZE)
618 return -EINVAL;
619 if (poff % arg.struct_size)
620 return -EINVAL;
621
622 pages = io_pin_pages(arg.user_addr, len, &nr_pages);
There ought to be a Smatch warning about that sort of thing here really but
there isn't yet.
623 if (IS_ERR(pages))
624 return PTR_ERR(pages);
625 ret = -EINVAL;
626 if (nr_pages != 1)
627 goto out_free;
628 if (ctx->user) {
629 ret = __io_account_mem(ctx->user, 1);
630 if (ret)
631 goto out_free;
632 }
633
634 reg = vmap(pages, 1, VM_MAP, PAGE_KERNEL);
635 if (reg) {
636 ctx->cq_wait_index = arg.nr_entries - 1;
637 WRITE_ONCE(ctx->cq_wait_page, pages);
638 WRITE_ONCE(ctx->cq_wait_arg, (void *) reg + poff);
639 return 0;
640 }
641 ret = -ENOMEM;
642 if (ctx->user)
643 __io_unaccount_mem(ctx->user, 1);
644 out_free:
645 io_pages_free(&pages, nr_pages);
646 return ret;
647 }
regards,
dan carpenter
next reply other threads:[~2024-10-30 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 11:40 Dan Carpenter [this message]
2024-10-30 13:22 ` [bug report] io_uring: add support for fixed wait regions Jens Axboe
2024-10-30 13:58 ` Dan Carpenter
2024-10-30 14:17 ` 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=3191af58-8707-4916-a657-ee376b36810a@stanley.mountain \
[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