On 03/07/2013 05:50 AM, Johannes Berg wrote:
On Wed, 2013-03-06 at 17:53 -0600, Larry Finger wrote:
However, that's a corner case, I don't think you ran into it. Since you
also didn't note any warnings, we can also discount a few cases that
would be code bugs and would leak.
I wonder if this is related to the first warning? The "new" object in
the first block would typically take ownership of the "ies" object.
Although I do not get any warnings, your patch and mine have made the kmemleak
scan now come up clean. I will continue testing and let you know.
Ok. I guess I'll apply my patch, and we can see about yours later (since
it's only a false positive, while mine actually fixes a potential leak).
Were you reconfiguring your AP's SSID by any chance?
No. All AP parameters were fixed - I get in trouble with my spouse whenever
anything changes on the APs.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
