Search Linux Wireless

Re: 2.6.32-rc5-git1 -- BUG kmalloc-8192: Poison overwritten (ath9k implicated)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 23, 2009 at 1:47 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:
> On Thu, Nov 19, 2009 at 3:19 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:
>> On Mon, Nov 16, 2009 at 5:08 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:
>>> 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.
>>
>> 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
--
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

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux