ae6874ba4b
Consider the case where a VD is deleted and the targetID of that VD is assigned to a newly created VD. If the sequence of deletion/addition of VD happens very quickly there is a possibility that second event (VD add) occurs even before the driver processes the first event (VD delete). As event processing is done in deferred context the device list remains the same (but targetID is re-used) so driver will not learn the VD deletion/additon. I/Os meant for the older VD will be directed to new VD which may lead to data corruption. Make driver detect the deleted VD as soon as possible based on the RaidMap update and block further I/O to that device. Link: https://lore.kernel.org/r/20210528131307.25683-4-chandrakanth.patil@broadcom.com Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com> Signed-off-by: Chandrakanth Patil <chandrakanth.patil@broadcom.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> |
||
|---|---|---|
| .. | ||
| Kconfig.megaraid | ||
| Makefile | ||
| mbox_defs.h | ||
| mega_common.h | ||
| megaraid_ioctl.h | ||
| megaraid_mbox.c | ||
| megaraid_mbox.h | ||
| megaraid_mm.c | ||
| megaraid_mm.h | ||
| megaraid_sas_base.c | ||
| megaraid_sas_debugfs.c | ||
| megaraid_sas_fp.c | ||
| megaraid_sas_fusion.c | ||
| megaraid_sas_fusion.h | ||
| megaraid_sas.h | ||