diff options
| author | Kashyap, Desai <kashyap.desai@lsi.com> | 2010-11-13 04:40:51 +0530 |
|---|---|---|
| committer | James Bottomley <James.Bottomley@suse.de> | 2010-12-21 12:24:08 -0600 |
| commit | b41c09d1afc2708b3fab395085f538e1fce9b571 (patch) | |
| tree | c92b67bd0f4aad01351bc383b32e01ef23a8e420 /Documentation/Intel-IOMMU.txt | |
| parent | a93c6b45df57332b1703e0dc6f99a1bafc17f5e3 (diff) | |
| download | kernel_samsung_espresso10-b41c09d1afc2708b3fab395085f538e1fce9b571.zip kernel_samsung_espresso10-b41c09d1afc2708b3fab395085f538e1fce9b571.tar.gz kernel_samsung_espresso10-b41c09d1afc2708b3fab395085f538e1fce9b571.tar.bz2 | |
[SCSI] mpt2sas: Sanity check for phy count is added using max phy count
Fix oops loading driver when there is direct attached
SEP device
The driver set max phys count to the value reported in sas iounit page
zero. However this page doesn't take into account additional virutal
phys. When sas topology event arrives, the phy count is larger than
expected, and the driver accesses memory array beyond the end of
allocated space, then oops. Manufacturing page 8 contains the info
on direct attached phys.
For this fix will making sure that sas topology event is not
processing phys greater than the expected phy count.
Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'Documentation/Intel-IOMMU.txt')
0 files changed, 0 insertions, 0 deletions