| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 8 Apr 2009 23:00:09 -0400 From: Bryan Donlan <bdonlan@...il.com> To: Justin Mattock <justinmattock@...il.com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: BUG kmalloc-2048: Invalid object pointer 0xf656ad80 On Wed, Apr 8, 2009 at 10:50 PM, Justin Mattock <justinmattock@...il.com> wrote: > On Wed, Apr 8, 2009 at 7:38 PM, Bryan Donlan <bdonlan@...il.com> wrote: >> On Wed, Apr 8, 2009 at 10:19 PM, Justin Mattock <justinmattock@...il.com> wrote: >>> doing a: >>> sudo /sbin/rmmod wl >>> (generated a bug message) >> [snip] >>> The kernel is tainted with nvidia, and a broadcom wl. >> >> Would this broadcom wl be the very module you're trying to remove? >> What makes you think this isn't a bug in this wl binary module? From >> the looks of the backtrace it's dying due to a free of a wild pointer >> right in the middle of the wl module - it certainly doesn't look like >> it came from some other subsystem... >> > > yup, > remove wl, in exchange > for ndiswrapper. and poof > this showed up.. The bug came up in the wl module's removal code - I'd suggest just not loading it in the first place. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists