When a user hot-adds a new hard disk and attaches it to an LSI Logic SAS controller on a VM, the newly added disk is not detected by the Linux guest OS. The 'fdisk -l
' command fails to list the newly added disk.
Simultaneously adding an LSI Logic SAS controller and a disk will result in a call trace in guest OS versions from Ubuntu 22.04 to Ubuntu 24.10, as shown below:
[ 176.181166] ================================================================================
[ 176.181167] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS
VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181] <TASK>
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
This is an upstream Linux kernel issue where the hot add event is not handled in time by the kernel.
Workaround:
After hot-adding an LSI Logic SAS disk, reboot the VM if the 'fdisk -l
' command fails to list the newly added disk.
Impact/Risks:
User may not be able to use hot-added LSI Logic SAS disk.