fcoe: Fix missing mutex_unlock in fcoe_sysfs_fcf_add error path
In this pending patch: http://patchwork.open-fcoe.org/patch/104/ Tomas Henzl noted that the error path when fcoe_fcf_device_add fails, was missing a mutex_unlock call. Not sure what staet the integration of the above patch is in, but if you could either merge this with it, or apply it on top of what you already have, that would be great. Thanks! Signed-off-by: Neil Horman <nhorman@tuxdriver.com> CC: thenzl@redhat.com Reported-by: thenzl@redhat.com Signed-off-by: Robert Love <robert.w.love@intel.com>
This commit is contained in:
parent
9d34876f82
commit
55d0ac5d28
|
@ -203,6 +203,7 @@ static int fcoe_sysfs_fcf_add(struct fcoe_fcf *new)
|
||||||
fcf_dev = fcoe_fcf_device_add(ctlr_dev, temp);
|
fcf_dev = fcoe_fcf_device_add(ctlr_dev, temp);
|
||||||
if (unlikely(!fcf_dev)) {
|
if (unlikely(!fcf_dev)) {
|
||||||
rc = -ENOMEM;
|
rc = -ENOMEM;
|
||||||
|
mutex_unlock(&ctlr_dev->lock);
|
||||||
goto out;
|
goto out;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue