7e324f734a
[ Upstream commit 0ee4ba13e09c9d9c1cb6abb59da8295d9952328b ]
While looping over shost's sdev list it is possible that one
of the drives is getting removed and its sas_target object is
freed but its sdev object remains intact.
Consequently, a kernel panic can occur while the driver is trying to access
the sas_address field of sas_target object without also checking the
sas_target object for NULL.
Link: https://lore.kernel.org/r/20211117104909.2069-1-sreekanth.reddy@broadcom.com
Fixes:
|
||
|---|---|---|
| .. | ||
| mpi | ||
| Kconfig | ||
| Makefile | ||
| mpt3sas_base.c | ||
| mpt3sas_base.h | ||
| mpt3sas_config.c | ||
| mpt3sas_ctl.c | ||
| mpt3sas_ctl.h | ||
| mpt3sas_debug.h | ||
| mpt3sas_scsih.c | ||
| mpt3sas_transport.c | ||
| mpt3sas_trigger_diag.c | ||
| mpt3sas_trigger_diag.h | ||
| mpt3sas_warpdrive.c | ||