On Wed, 2013-06-19 at 07:22 -0700, Ben Greear wrote: > > I'm not really sure this is worth it -- you found the bug with > > kmemleak() after all. Having very specific things for all of this > > doesn't really seem worth it. > > kmemleak didn't show the bss leaking though, so I spent several days > thinking ies pointers were being corrupted somehow. I think the code > is not that intrusive, and since drivers also take bss refs, the problems > could come back in the future. Fair enough, I'll think about it some more. I don't think drivers are really that much of a problem though. > I didn't actually audit the drivers since I am not using that hardware, > by the way. Right. > I started porting some patches to wireless-next yesterday..think that > would be a good enough tree to patch against? Probably OK, I only have few patches right now. I also just posted two patches to address parts of this problem though, can you review those too? johannes -- 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
