diff options
| author | James Bottomley <JBottomley@Parallels.com> | 2015-03-18 15:56:16 -0700 |
|---|---|---|
| committer | James Bottomley <JBottomley@Parallels.com> | 2015-03-31 08:53:36 +0300 |
| commit | 11e52a699afff576606ceb6cf697270459f1a4aa (patch) | |
| tree | 7b70436fc1ce49d16fe4b669bf8c1394d6fa35e1 /drivers/misc/mic | |
| parent | 6302ce4d80aa82b3fdb5c5cd68e7268037091b47 (diff) | |
| download | op-kernel-dev-11e52a699afff576606ceb6cf697270459f1a4aa.zip op-kernel-dev-11e52a699afff576606ceb6cf697270459f1a4aa.tar.gz | |
enclosure: fix WARN_ON removing an adapter in multi-path devices
We have peculiar problems with multi-path and enclosures: physically, we know
each bay can only be occupied by a single disk device. However in multi-path,
it appears we have many (because each path to the device appears in Linux as a
different kernel device). We try to fix this by only having the last seen
device show up in the bay.
Sysfs gets very annoyed if we try to manipulate links when the kobject sysfs
directory (kobj.sd) doesn't exist and drops a huge WARN_ON which most users
panic and report an oops for. This happens on a few path removal situations
and IBM reports seeing it when one of their multi-path adapters is removed.
Add a check to enclosure device removal for the existence the sysfs directory
containing both the forward and back links so that the remnants (if any) get
removed in either direction but no scary warnings are dumped.
Reported-by: Wen Xiong <wenxiong@linux.vnet.ibm.com>
Tested-by: Wen Xiong <wenxiong@linux.vnet.ibm.com>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'drivers/misc/mic')
0 files changed, 0 insertions, 0 deletions
