summaryrefslogtreecommitdiff
path: root/drivers/scsi/aacraid
diff options
context:
space:
mode:
authorRaghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>2017-12-27 07:34:48 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2018-01-04 07:26:43 +0300
commitfe5237590bb033ad6b7312b0ef62a2d7d5c4141f (patch)
treec03b2a2f58b0659f6064f3c294d54eba3f647cde /drivers/scsi/aacraid
parent8a30e50b72ca08c78474db514531ce5d9ae00fa4 (diff)
downloadlinux-fe5237590bb033ad6b7312b0ef62a2d7d5c4141f.tar.xz
scsi: aacraid: Skip schedule rescan in case of kdump
There is a chance of the driver to be stuck in kdump if drives start acting up in kdump discovery process and the kernel decides to send eh resets, which would prompt rescan to be scheduled. Do not perform a rescan in kdump context, since we do not expect a hotplug event during kdump and all the devices are going to go away anyway. Signed-off-by: Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/aacraid')
-rw-r--r--drivers/scsi/aacraid/commsup.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/scsi/aacraid/commsup.c b/drivers/scsi/aacraid/commsup.c
index 706aba0ed726..f0c3e7dbf60a 100644
--- a/drivers/scsi/aacraid/commsup.c
+++ b/drivers/scsi/aacraid/commsup.c
@@ -33,6 +33,7 @@
#include <linux/kernel.h>
#include <linux/init.h>
+#include <linux/crash_dump.h>
#include <linux/types.h>
#include <linux/sched.h>
#include <linux/pci.h>
@@ -1675,7 +1676,7 @@ out:
* Issue bus rescan to catch any configuration that might have
* occurred
*/
- if (!retval) {
+ if (!retval && !is_kdump_kernel()) {
dev_info(&aac->pdev->dev, "Scheduling bus rescan\n");
aac_schedule_safw_scan_worker(aac);
}