From: Jason Gunthorpe <jgg@ziepe.ca>
To: Samuel Moelius <sam.moelius@trailofbits.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"open list:IOMMUFD" <iommu@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/iommufd: avoid selftest dirty bitmap size wrap
Date: Tue, 9 Jun 2026 14:52:31 -0300 [thread overview]
Message-ID: <20260609175231.GN2764304@ziepe.ca> (raw)
In-Reply-To: <20260609005517.1241471.82360db24575.iommufd-test-dirty-bitmap-size-wrap@trailofbits.com>
On Tue, Jun 09, 2026 at 12:55:18AM +0000, Samuel Moelius wrote:
> IOMMU_TEST_OP_DIRTY sizes its temporary dirty bitmap from
> length / page_size. Very large selftest ranges can make the
> DIV_ROUND_UP() additions wrap before allocation, producing a
> zero-length allocation while the later test_bit() loop still walks the
> original number of bits.
>
> Reject bitmap sizes whose byte or unsigned-long counts cannot be
> computed without overflow, and use array_size() for the allocation.
>
> Assisted-by: Codex:gpt-5.5-cyber-preview
> Signed-off-by: Samuel Moelius <sam.moelius@trailofbits.com>
> ---
> drivers/iommu/iommufd/selftest.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iommu/iommufd/selftest.c b/drivers/iommu/iommufd/selftest.c
> index af07c642a526..08c36d9ba3e4 100644
> --- a/drivers/iommu/iommufd/selftest.c
> +++ b/drivers/iommu/iommufd/selftest.c
> @@ -1685,8 +1685,9 @@ static int iommufd_test_dirty(struct iommufd_ucmd *ucmd, unsigned int mockpt_id,
> unsigned long page_size, void __user *uptr,
> u32 flags)
> {
> - unsigned long i, max;
> struct iommu_test_cmd *cmd = ucmd->cmd;
> + unsigned long i, max, nr_bytes;
> + unsigned long nr_longs;
> struct iommufd_hw_pagetable *hwpt;
> struct mock_iommu_domain *mock;
> int rc, count = 0;
> @@ -1706,14 +1707,22 @@ static int iommufd_test_dirty(struct iommufd_ucmd *ucmd, unsigned int mockpt_id,
> }
>
> max = length / page_size;
> - tmp = kvzalloc(DIV_ROUND_UP(max, BITS_PER_LONG) * sizeof(unsigned long),
> + if (check_add_overflow(max, BITS_PER_LONG - 1, &nr_longs) ||
> + check_add_overflow(max, BITS_PER_BYTE - 1, &nr_bytes)) {
We can just limit length to something, it isn't like this:
> + tmp = kvzalloc(array_size(nr_longs, sizeof(unsigned long)),
> GFP_KERNEL_ACCOUNT);
> if (!tmp) {
Will work with big numbers anyhow.
I suggest length > SZ_16M * page_size with a check mul overflow
Jason
prev parent reply other threads:[~2026-06-09 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 0:55 Samuel Moelius
2026-06-09 17:52 ` Jason Gunthorpe [this message]
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=20260609175231.GN2764304@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sam.moelius@trailofbits.com \
--cc=will@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 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®