All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sean Christopherson" <seanjc@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v6 04/18] KVM: selftests: Add helper to generate random u64 in range [min,max]
Date: Wed, 10 Jun 2026 01:01:27 +0000	[thread overview]
Message-ID: <20260610010127.A86D81F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610005338.2967132-5-seanjc@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] kvm_random_u64_in_range() silently fails to cover the requested range because it relies on kvm_random_u64(), which leaves bits 31 and 63 perpetually zero.
--

commit 7a6b1751be67e53b72972ac1a299690dc79f537f
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). This function returns a
random u64 in the inclusive range of [min, max] using a struct kvm_random_state.

> 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)
[ ... ]
> +/* 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);
> +
> +	range = max - min;
> +	if (range == ULLONG_MAX)
> +		return value;
> +
> +	return min + (value % (range + 1));

[Severity: Medium]
Will this reliably cover the requested range?

Since kvm_random_u64() constructs its return value by concatenating two
outputs from kvm_random_u32(), and kvm_random_u32() only returns values up
to 0x7FFFFFFE, bits 31 and 63 of the 64-bit output are always 0.

When this skewed 64-bit value is used to bound the output range, significant
portions of the requested range become completely unreachable. For example, in
a 32-bit range, values >= 0x80000000 will never be generated.

> +}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260610005338.2967132-1-seanjc@google.com?part=4

  reply	other threads:[~2026-06-10  1:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  0:53 [PATCH v6 00/18] KVM: selftests: Add eventfd+VFIO IRQ test Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 01/18] KVM: selftests: Build and link selftests/vfio/lib into KVM selftests Sean Christopherson
2026-06-10  1:03   ` sashiko-bot
2026-06-10  0:53 ` [PATCH v6 02/18] KVM: selftests: Add macros to read/write+sync to/from guest memory Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 03/18] KVM: selftests: Rename guest_rng to kvm_rng Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 04/18] KVM: selftests: Add helper to generate random u64 in range [min,max] Sean Christopherson
2026-06-10  1:01   ` sashiko-bot [this message]
2026-06-10  0:53 ` [PATCH v6 05/18] KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) test Sean Christopherson
2026-06-10  1:08   ` sashiko-bot
2026-06-10  0:53 ` [PATCH v6 06/18] KVM: selftests: Add helper to get host IRQ from device MSI-X for IRQ bypass test Sean Christopherson
2026-06-10  1:01   ` sashiko-bot
2026-06-10  0:53 ` [PATCH v6 07/18] KVM: selftests: Add VFIO device support to eventfd IRQ test Sean Christopherson
2026-06-10  1:05   ` sashiko-bot
2026-06-10  0:53 ` [PATCH v6 08/18] KVM: selftests: Add a helper to set proc IRQ affinity for " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 09/18] KVM: selftests: Verify interrupts are received when IRQ affinity changes in " Sean Christopherson
2026-06-10  1:06   ` sashiko-bot
2026-06-10  0:53 ` [PATCH v6 10/18] KVM: selftests: Add option to set empty routing between IRQs in eventfd " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 11/18] KVM: selftests: Make number of IRQs configurable in " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 12/18] KVM: selftests: Verify non-postable IRQ remapping " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 13/18] KVM: selftests: Add kvm_gettid() wrapper and convert users Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 14/18] KVM: selftests: Add kvm_sched_getaffinity() " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 15/18] KVM: selftests: Add a utility to pin a task to a random CPU, given a CPU set Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 16/18] KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ test Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 17/18] KVM: selftests: Make number of vCPUs configurable " Sean Christopherson
2026-06-10  0:53 ` [PATCH v6 18/18] 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=20260610010127.A86D81F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kvm@vger.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.