diff options
| author | Martin Wilck <[email protected]> | 2025-03-21 22:33:19 +0000 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2025-04-03 14:08:03 +0000 |
| commit | a2d5a0072235a69749ceb04c1a26dc75df66a31a (patch) | |
| tree | 4504614f2575e9b40113be33e85344334ae18c27 /drivers/pwm/pwm-stm32.c | |
| parent | scsi: pm80xx: Set phy_attached to zero when device is gone (diff) | |
| download | kernel-a2d5a0072235a69749ceb04c1a26dc75df66a31a.tar.gz kernel-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 <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Cc: Randy Wright <[email protected]>
Acked-by: Don Brace <[email protected]>
Tested-by: Don Brace <[email protected]>
Reviewed-by: Lee Duncan <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'drivers/pwm/pwm-stm32.c')
0 files changed, 0 insertions, 0 deletions