forked from Minki/linux
59db5a931b
Issue: This issue is applicable to scenario when JBOD sequence map is unavailable (memory allocation for JBOD sequence map failed) to driver but feature is supported by firmware. If the driver sends a JBOD IO by not adding 255 (MAX_PHYSICAL_DEVICES - 1) to device ID when underlying firmware supports JBOD sequence map, it will lead to the IO failure. Fix: For JBOD IOs, driver will not use the RAID map to fetch the devhandle if JBOD sequence map is unavailable. Driver will set Devhandle to 0xffff and Target ID to 'device ID + 255 (MAX_PHYSICAL_DEVICES - 1)'. Signed-off-by: Sumit Saxena <sumit.saxena@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 | ||