From: Miles Lane <miles.lane@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Felix Bitterli <ic.felix@gmail.com>
Subject: Re: 2.6.32-rc5-git1 -- BUG kmalloc-8192: Poison overwritten (ath9k implicated)
Date: Mon, 16 Nov 2009 19:41:47 -0500 [thread overview]
Message-ID: <a44ae5cd0911161641n36d3c746pb69a9cac1eba1784@mail.gmail.com> (raw)
In-Reply-To: <43e72e890911161515q64ff527cyefd7d769f3c501b@mail.gmail.com>
On Mon, Nov 16, 2009 at 6:15 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Tue, Oct 20, 2009 at 1:45 PM, Miles Lane <miles.lane@gmail.com> 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.
Miles
next prev parent reply other threads:[~2009-11-17 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 21:45 Miles Lane
2009-11-16 23:15 ` Luis R. Rodriguez
2009-11-17 0:41 ` Miles Lane [this message]
2009-11-17 1:08 ` Luis R. Rodriguez
2009-11-19 23:19 ` Luis R. Rodriguez
2009-11-23 21:47 ` Luis R. Rodriguez
2009-12-01 7:54 ` Luis R. Rodriguez
2009-12-02 17:34 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-10-20 21:11 Miles Lane
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=a44ae5cd0911161641n36d3c746pb69a9cac1eba1784@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=ic.felix@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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®