Re: [PATCH v6 09/18] KVM: selftests: Verify interrupts are received when IRQ affinity changes in IRQ test

[Sean Christopherson <seanjc@google.com>]

On Wed, Jun 10, 2026, sashiko-bot@kernel.org wrote:
> > @@ -192,7 +198,12 @@ int main(int argc, char **argv)
> >  		printf("Using device %s MSI-X[%d] (IRQ-%u)\n", device_bdf, msix,
> >  		       irq);
> >  	} else {
> > +		TEST_ASSERT(!irq_affinity,
> > +			    "Setting IRQ affinity (-a) requires a backing device (-d)");
> > +
> >  		eventfd = kvm_new_eventfd();
> > +		irq = -1;
> > +		irq_cpu = -1;
> >  	}
> 
> [Severity: Low]
> Is irq_cpu used uninitialized here when the test is run with -d but without -a?
> 
> When a backing device is specified (-d), the code enters the if (device_bdf)
> block and irq_cpu remains uninitialized. If a vCPU times out waiting for an
> interrupt, the TEST_ASSERT macro evaluates and passes the uninitialized
> irq_cpu to the variadic format string, printing garbage values.

Gah, I meant to initialize it to -1 (hence the signed %d instead of %u).