Return-path: Received: from mail-we0-f175.google.com ([74.125.82.175]:53449 "EHLO mail-we0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751676AbaCHXLU (ORCPT ); Sat, 8 Mar 2014 18:11:20 -0500 MIME-Version: 1.0 In-Reply-To: <2894930.q0nCt6o0pg@debian64> References: <1394226709-10763-1-git-send-email-khoroshilov@ispras.ru> <2894930.q0nCt6o0pg@debian64> From: Krishna Chaitanya Date: Sun, 9 Mar 2014 04:40:58 +0530 Message-ID: (sfid-20140309_001141_849438_86247B83) Subject: Re: [PATCH] p54usb: fix leaks at failure path in p54u_probe() To: Christian Lamparter Cc: Alexey Khoroshilov , "John W. Linville" , linux-wireless , netdev , linux-kernel@vger.kernel.org, ldv-project@linuxtesting.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, Mar 9, 2014 at 4:38 AM, Christian Lamparter wrote: > On Sunday, March 09, 2014 04:14:32 AM Krishna Chaitanya wrote: >> On Sat, Mar 8, 2014 at 2:41 AM, Alexey Khoroshilov >> wrote: >> > If p54u_load_firmware() fails, p54u_probe() does not deallocate >> > already allocated resources. The patch adds proper failure handling. >> > >> > Found by Linux Driver Verification project (linuxtesting.org). >> > >> > Signed-off-by: Alexey Khoroshilov >> > --- >> > drivers/net/wireless/p54/p54usb.c | 4 ++++ >> > 1 file changed, 4 insertions(+) >> > >> > diff --git a/drivers/net/wireless/p54/p54usb.c b/drivers/net/wireless/p54/p54usb.c >> > index 6e635cfa24c8..5df74503fd4f 100644 >> > --- a/drivers/net/wireless/p54/p54usb.c >> > +++ b/drivers/net/wireless/p54/p54usb.c >> > @@ -1053,6 +1053,10 @@ static int p54u_probe(struct usb_interface *intf, >> > priv->upload_fw = p54u_upload_firmware_net2280; >> > } >> > err = p54u_load_firmware(dev, intf); >> > + if (err) { >> > + usb_put_dev(udev); >> > + p54_free_common(dev); >> > + } >> > return err; >> > } >> The load_firmware puts down the reference >> in case of error. Only free is required here. > No, the put is required too... But let me explain: > > p54u_load_firmware calls usb_get_dev(udev) before it requests the firmware > load. The Reason is: the firmware callback is usually run in another thread > (usually it's pretty quick, but due to timeouts it could take up to 60 seconds > - or at least it did when I wrote it). Therefore I found it appropriate to give > that request callback its "reference++" as it needs the "udev" too (e.g.: for > dev_info, dev_err and releasing the driver if the device couldn't be > initialized). > Thanks Christian and Alexey, you answered my next question as well :-).