Public bug reported:
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.
[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
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-azure (Ubuntu Jammy)
Importance: High
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu)
Status: New => In Progress
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996806
Title:
Azure: Jammy fio test causes panic
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Bug description:
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.
[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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
