[PATCH 0/1][SRU][jammy:linux-azure] Azure: Jammy fio test causes panic

[Tim Gardner]

BugLink: https://bugs.launchpad.net/bugs/1996806

SRU Justification

[Impact]

During Storage performance tests, 16 disks are attached and fio is ran. The fio
command does not consistently result in a kernel panic, but the test runs fio
enough times to result in consistent kernel panic. The panic is most often
observed on instances with many cores and disks.

This panic fix qualifies for a respin.

[Test Case]

Using an instance with 96 cores and 16 disks:

sudo fio --ioengine=libaio --bs=1024K --filename=/dev/sda:/dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi:/dev/sdj:/dev/sdk:/dev/sdl:/dev/sdm:/dev/sdn:/dev/sdo:/dev/sdp --readwrite=read --runtime=120 --iodepth=32 --numjob=96 --name=iteration23 --direct=1 --size=8192M --group_reporting --overwrite=1

[Regression Potential]

The fix is an upstream patch from 5.17, commit 0bd2fbee9d0b7f801a9c0264d90b1e0d8053f395 ('scsi:
storvsc: Fix unsigned comparison to zero'). Regression potential is low.

[Other Info]

SF: #00346757