[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50A3D0E1.4060209@ruggedcom.com>
Date: Wed, 14 Nov 2012 12:12:01 -0500
From: Richard Retanubun <richardretanubun@...gedcom.com>
To: Johan Hovold <jhovold@...il.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>,
Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Tang Nguyen <TangNguyen@...gedcom.com>,
linux-usb mailing list <linux-usb@...r.kernel.org>
Subject: Re: kmemleak report on isp1763 and sierra MC8705
On 10/11/12 09:30 AM, Johan Hovold wrote:
Hi Johan,
> There was a reference-count fix for the probe error path that went in to
> v3.5. Haven't read all the details on how you trigger your leak, but at
> the face of it, it could be related.
>
> Have a look at 0658a3366db7e27fa ("usb: use usb_serial_put in
> usb_serial_probe errors). If related, you should be seeing "Ignoring
> blacklisted interface #n" messages when you enable debug (e.g. #define
> DEBUG) in the sierra driver.
That was it! Thanks so much for the research.
I can apply it cleanly to 3.0.22 and see usb_release_dev() being called and thus no more kmemleak.
>
> Greg, it seems to me that the fix referred to above should be backported
> to the earlier stable trees either way.
I would vote "yes" for this also.
While my setup circumstances may be a corner case, (modem kept resetting to re-establish PPP connection)
it was leaking 1192 bytes per occurrence.
Thanks for everyone's time.
-- Richard Retanubun.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists