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 <[email protected]>
CC: [email protected]
Reported-by: [email protected]
Signed-off-by: Robert Love <[email protected]>

diff --git a/drivers/scsi/fcoe/fcoe_ctlr.c b/drivers/scsi/fcoe/fcoe_ctlr.c
index 75efdbc54ef8f5ce5aa36c23212af0dbdc806cce..2aba32f12f13a85b16ec934bbabbe650de165f47 100644 (file)
--- a/drivers/scsi/fcoe/fcoe_ctlr.c
+++ b/drivers/scsi/fcoe/fcoe_ctlr.c
@@ -203,6 +203,7 @@ static int fcoe_sysfs_fcf_add(struct fcoe_fcf *new)
                fcf_dev = fcoe_fcf_device_add(ctlr_dev, temp);
                if (unlikely(!fcf_dev)) {
                        rc = -ENOMEM;
+                       mutex_unlock(&ctlr_dev->lock);
                        goto out;
                }