On Mon, Nov 16, 2009 at 4:41 PM, Miles Lane <miles.lane@xxxxxxxxx> wrote: > On Mon, Nov 16, 2009 at 6:15 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >> On Tue, Oct 20, 2009 at 1:45 PM, Miles Lane <miles.lane@xxxxxxxxx> wrote: >>> Let me know if you want my .config file. I think this was triggered by >>> suspending my laptop. >>> >>> BUG kmalloc-8192: Poison overwritten >> >> Thanks for your report Miles. >> >> Are you using Linus' tree? Felix wrote some patches that got rid of >> the rate control private area which we kmalloc/kfree and at least one >> user reported that these patches fixed a memory leak. I'm curious if >> the same patches would resolve this issue. >> >> Only thing is these patches apply against wireless-testing and not >> 2.6.32. To test them you'd have to pull wireless-testing master to >> your tree and then apply the patches both before and after. >> >> Would you be up to try that? > > Yes, definitely. Thanks. I will try to accomplish this and let you > know if I get stuck. OK, not sure if a merge of wireless-testing will be clean so you may want to just clone fresh.. Anyway after you get wireless-testing bits you'll want to apply these: http://patchwork.kernel.org/patch/60127/ http://patchwork.kernel.org/patch/60128/ http://patchwork.kernel.org/patch/60126/ If you want to merge wireless-testing you can try: git merge git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git master If that'd doesn't gos smooth just clone it and I think you should be able to safely --reference your current tree for objects for Linus' tree. Luis -- 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
