Hi, On Mon, Apr 22, 2013 at 7:50 PM, Bing Zhao <bzhao@xxxxxxxxxxx> wrote: > Thanks for reporting this issue. > Please find attached the patch and try it on your XO4. > > I will resend the patch to the list if it works for you. This does seem to make the kmemleak report go away. However, strangely, it seems to make a whole bunch of kmemleak reports *appear*, as if the struct netdev is not being destroyed, and more. I guess this could just be a kmemleak oddity but it is strange that it did not appear before this patch. Trying to look for possible causes (memory corruption?), I can't see any code that serializes scan_delay_timer_fn with mwifiex_close(), so mwifiex_close freeing the scan data while scan_delay_timer_fn is using it could cause badness to happen. However I haven't yet figured out how to trigger scan_delay_timer_fn to execute even once (any tips?). The fact that scan_delay_timer_fn isn't executing at all means that its not related to the kmemleak oddness, which must have another cause or explanation. I will investigate more tomorrow. Thanks Daniel -- 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
