There are leaks of resources allocated by wlan_setup() and usb_dev refcnt
on failure paths in prism2sta_probe_usb().

The patch adds appropriate deallocations and removes invalid code
from hfa384x_corereset() failure handling.
unregister_wlandev() is wrong because it is not registered yet.
hfa384x_destroy() is just noop in init state.

Found by Linux Driver Verification project (linuxtesting.org).

Signed-off-by: Alexey Khoroshilov <khoroshi...@ispras.ru>
---
 drivers/staging/wlan-ng/prism2usb.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/wlan-ng/prism2usb.c 
b/drivers/staging/wlan-ng/prism2usb.c
index b401974fb282..4739c14d8359 100644
--- a/drivers/staging/wlan-ng/prism2usb.c
+++ b/drivers/staging/wlan-ng/prism2usb.c
@@ -140,11 +140,9 @@ static int prism2sta_probe_usb(struct usb_interface 
*interface,
                                           prism2_reset_holdtime,
                                           prism2_reset_settletime, 0);
                if (result != 0) {
-                       unregister_wlandev(wlandev);
-                       hfa384x_destroy(hw);
                        result = -EIO;
                        dev_err(&interface->dev, "hfa384x_corereset() 
failed.\n");
-                       goto failed;
+                       goto failed_reset;
                }
        }
 
@@ -159,11 +157,15 @@ static int prism2sta_probe_usb(struct usb_interface 
*interface,
        if (register_wlandev(wlandev) != 0) {
                dev_err(&interface->dev, "register_wlandev() failed.\n");
                result = -EIO;
-               goto failed;
+               goto failed_register;
        }
 
        goto done;
 
+failed_register:
+       usb_put_dev(dev);
+failed_reset:
+       wlan_unsetup(wlandev);
 failed:
        kfree(wlandev);
        kfree(hw);
-- 
1.8.3.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to