From: sashiko-bot@kernel.org
To: "Sean Christopherson" <seanjc@google.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
"Marc Zyngier" <maz@kernel.org>,
"Oliver Upton" <oupton@kernel.org>
Subject: Re: [PATCH v8 06/20] KVM: selftests: Add helper to generate random u64 in range [min,max]
Date: Fri, 26 Jun 2026 21:44:44 +0000 [thread overview]
Message-ID: <20260626214444.C52711F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260626213534.3866178-7-seanjc@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] kvm_random_u64() never sets bits 31 and 63, causing kvm_random_u64_in_range() to have severe blind spots.
--
commit 5a3dcffb3cb35a622072ea5194b7875f774cb3a7
Author: Josh Hilke <jrhilke@google.com>
KVM: selftests: Add helper to generate random u64 in range [min,max]
Introduce kvm_random_u64_in_range(state, min, max) to return a random u64
within an inclusive range.
> diff --git a/tools/testing/selftests/kvm/lib/test_util.c b/tools/testing/selftests/kvm/lib/test_util.c
> index e98ca7ef439c4..e208a57f190cf 100644
> --- a/tools/testing/selftests/kvm/lib/test_util.c
> +++ b/tools/testing/selftests/kvm/lib/test_util.c
[ ... ]
> @@ -42,6 +42,24 @@ u32 kvm_random_u32(struct kvm_random_state *state)
> return state->seed;
> }
>
> +/* Returns a random u64 in the inclusive range [min, max] */
> +u64 kvm_random_u64_in_range(struct kvm_random_state *state, u64 min,
> + u64 max)
> +{
> + u64 value;
> + u64 range;
> +
> + TEST_ASSERT(min <= max, "PEBKAC, min = 0x%lx, max = 0x%lx", min, max);
> +
> + value = kvm_random_u64(state);
[Severity: Medium]
Will this result in severe blind spots within the generated range?
Looking at how the random value is constructed:
tools/testing/selftests/kvm/include/test_util.h:kvm_random_u64() {
return ((u64)kvm_random_u32(state) << 32) | kvm_random_u32(state);
}
And considering kvm_random_u32() limits its return value with a modulo of
((u32)(1 << 31) - 1), it appears bits 31 and 63 will always remain zero.
Does this mean the subsequent modulo operation in this function:
> +
> + range = max - min;
> + if (range == ULLONG_MAX)
> + return value;
> +
> + return min + (value % (range + 1));
> +}
will fail to cover large portions of requested ranges? For example, if a
test requests a 4GB range, could this only ever return values in the lower
2GB of that range?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626213534.3866178-1-seanjc@google.com?part=6
next prev parent reply other threads:[~2026-06-26 21:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:35 [PATCH v8 00/20] KVM: selftests: Add eventfd+VFIO IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 01/20] KVM: selftests: Build and link selftests/vfio/lib into KVM selftests Sean Christopherson
2026-06-26 21:44 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 02/20] KVM: selftests: Add macros to read/write+sync to/from guest memory Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 03/20] KVM: selftests: Rename guest_rng to kvm_rng Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 04/20] KVM: selftests: Initialize the default/global pRNG during kvm_selftest_init() Sean Christopherson
2026-06-26 21:48 ` sashiko-bot
2026-06-26 21:59 ` Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 05/20] KVM: selftests: Seed libc's RNG before using it to generate a seed for KVM's pRNG Sean Christopherson
2026-06-26 21:43 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 06/20] KVM: selftests: Add helper to generate random u64 in range [min,max] Sean Christopherson
2026-06-26 21:44 ` sashiko-bot [this message]
2026-06-26 21:35 ` [PATCH v8 07/20] KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 08/20] KVM: selftests: Add helper to get host IRQ from device MSI-X for IRQ bypass test Sean Christopherson
2026-06-26 21:42 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 09/20] KVM: selftests: Add VFIO device support to eventfd IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 10/20] KVM: selftests: Add a helper to set proc IRQ affinity for " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 11/20] KVM: selftests: Verify interrupts are received when IRQ affinity changes in " Sean Christopherson
2026-06-26 21:46 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 12/20] KVM: selftests: Add option to set empty routing between IRQs in eventfd " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 13/20] KVM: selftests: Make number of IRQs configurable in " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 14/20] KVM: selftests: Verify non-postable IRQ remapping " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 15/20] KVM: selftests: Add kvm_gettid() wrapper and convert users Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 16/20] KVM: selftests: Add kvm_sched_getaffinity() " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 17/20] KVM: selftests: Add a utility to pin a task to a random CPU, given a CPU set Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 18/20] KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 19/20] KVM: selftests: Make number of vCPUs configurable " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 20/20] KVM: selftests: Add xAPIC support in eventfd " Sean Christopherson
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=20260626214444.C52711F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seanjc@google.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 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.