diff options
| author | Martin Wilck <mwilck@suse.com> | 2025-03-21 23:33:19 +0100 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2025-04-03 10:08:03 -0400 |
| commit | a2d5a0072235a69749ceb04c1a26dc75df66a31a (patch) | |
| tree | 4504614f2575e9b40113be33e85344334ae18c27 /rust/helpers/helpers.c | |
| parent | f7b705c238d1483f0a766e2b20010f176e5c0fb7 (diff) | |
| download | linux-stable-a2d5a0072235a69749ceb04c1a26dc75df66a31a.tar.gz linux-stable-a2d5a0072235a69749ceb04c1a26dc75df66a31a.tar.bz2 linux-stable-a2d5a0072235a69749ceb04c1a26dc75df66a31a.zip | |
scsi: smartpqi: Use is_kdump_kernel() to check for kdump
The smartpqi driver checks the reset_devices variable to determine
whether special adjustments need to be made for kdump. This has the
effect that after a regular kexec reboot, some driver parameters such as
max_transfer_size are much lower than usual. More importantly, kexec
reboot tests have revealed memory corruption caused by the driver log
being written to system memory after a kexec.
Fix this by testing is_kdump_kernel() rather than reset_devices where
appropriate.
Fixes: 058311b72f54 ("scsi: smartpqi: Add fw log to kdump")
Signed-off-by: Martin Wilck <mwilck@suse.com>
Link: https://lore.kernel.org/r/20250321223319.109250-1-mwilck@suse.com
Cc: Randy Wright <rwright@hpe.com>
Acked-by: Don Brace <don.brace@microchip.com>
Tested-by: Don Brace <don.brace@microchip.com>
Reviewed-by: Lee Duncan <lduncan@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'rust/helpers/helpers.c')
0 files changed, 0 insertions, 0 deletions