mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Donlan <bdonlan@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BUG kmalloc-2048: Invalid object pointer 0xf656ad80
Date: Wed, 8 Apr 2009 23:00:09 -0400	[thread overview]
Message-ID: <3e8340490904082000h39a19ad8mc2c2fe9a9ab88685@mail.gmail.com> (raw)
In-Reply-To: <dd18b0c30904081950t4ce7186fy4430ceeb36540232@mail.gmail.com>

On Wed, Apr 8, 2009 at 10:50 PM, Justin Mattock <justinmattock@gmail.com> wrote:
> On Wed, Apr 8, 2009 at 7:38 PM, Bryan Donlan <bdonlan@gmail.com> wrote:
>> On Wed, Apr 8, 2009 at 10:19 PM, Justin Mattock <justinmattock@gmail.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.

  reply	other threads:[~2009-04-09  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  2:19 Justin Mattock
2009-04-09  2:38 ` Bryan Donlan
2009-04-09  2:50   ` Justin Mattock
2009-04-09  3:00     ` Bryan Donlan [this message]
2009-04-09  3:06       ` Justin Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e8340490904082000h39a19ad8mc2c2fe9a9ab88685@mail.gmail.com \
    --to=bdonlan@gmail.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®