The bug was found via the memory-leak static analysis tool that we have built on top of C-Atlas framework from EnSoft. You can check it out (http://www.ensoftcorp.com/atlas/). Thanks for clarifying things! ~Ahmed On Wed, Dec 3, 2014 at 2:48 AM, Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > This is a real bug, but it's very minor. To trigger it, you would have > to modprobe and rmmod many many times in a loop. If you report these > sorts of minor bugs when the code is new, then most times people fix > them but this one is old I doubt anyone is motivated to fix it. Fixing > it seems a little complicated to me as well. > > I suppose that linux-kernel@xxxxxxxxxxxxxxx is the correct mailing list > to report this but the truth is that no one reads that list. > > Anyway, it seems that you have written a good bug finding tool. :) > Congratulations for that! > > regards, > dan carpenter _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
