mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: 2.6.32-rc5-git1 -- BUG kmalloc-8192: Poison overwritten (ath9k  implicated)
Date: Mon, 30 Nov 2009 23:54:26 -0800	[thread overview]
Message-ID: <43e72e890911302354i1b17265ckb3aa81171a24174b@mail.gmail.com> (raw)
In-Reply-To: <43e72e890911231347k48f105dcw24dd99c1c39f034@mail.gmail.com>

On Mon, Nov 23, 2009 at 1:47 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Thu, Nov 19, 2009 at 3:19 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> On Mon, Nov 16, 2009 at 5:08 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>>> On Mon, Nov 16, 2009 at 4:41 PM, Miles Lane <miles.lane@gmail.com> wrote:
>>>> 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.
>>>
>>> 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.
>>
>> Miles I see no reply from you yet so I backported the patches in
>> question for you. Can you please try 2.6.32-rc7 and apply these
>> patches on top:
>>
>> http://bombadil.infradead.org/~mcgrof/patches/ath9k/2009/11-19/70-mac80211-total-ampdu-tx-info.patch
>> http://bombadil.infradead.org/~mcgrof/patches/ath9k/2009/11-19/71-ath9k-remove-tx_info_priv.patch
>
> Miles, any luck testing this?

Miles -- poke. The patches provided should apply on Linus' tree,
please let us know if they fix the issue you reported.

  Luis

  reply	other threads:[~2009-12-01  7:54 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
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 [this message]
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=43e72e890911302354i1b17265ckb3aa81171a24174b@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=nbd@openwrt.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®