diff options
| author | Chandrakanth Patil <chandrakanth.patil@broadcom.com> | 2019-06-25 16:34:26 +0530 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2019-06-27 00:07:35 -0400 |
| commit | 59db5a931bbe73f4d03dadb7365d0da2d425e769 (patch) | |
| tree | a16253d329d8bac847c5d857f393d176a3300367 /Documentation/block | |
| parent | 798d44b04f48237b3415c1066fd8f4d8b8fbb53b (diff) | |
| download | linux-59db5a931bbe73f4d03dadb7365d0da2d425e769.tar.bz2 | |
scsi: megaraid_sas: Handle sequence JBOD map failure at driver level
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>
Diffstat (limited to 'Documentation/block')
0 files changed, 0 insertions, 0 deletions