linux-kernel - Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B182F79.7060103@gmail.com>
Date:	Thu, 03 Dec 2009 13:36:57 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ath9k-devel@...ts.ath9k.org
Subject: Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten

On 12/02/09 15:16, Luis R. Rodriguez wrote:
> On Wed, Dec 2, 2009 at 2:27 PM, Justin Mattock<justinmattock@...il.com>  wrote:
>> I have no idea what this is:
>> (first time I've seen this);
>>
>>
>> [   13.055592] =============================================================================
>> [   13.055865] BUG kmalloc-8192: Poison overwritten
>> [   13.056046] -----------------------------------------------------------------------------
>
> I believe this means we write to an area in memory after we freed an skb.
>
>> [   13.056366] INFO: 0xffff88003290a100-0xffff88003290a143. First byte
>> 0x50 instead of 0x6b
>> [   13.056366] INFO: Allocated in ath_rxbuf_alloc+0x25/0x94 [ath]
>> age=8898 cpu=0 pid=892
>> [   13.056366] INFO: Freed in skb_release_data+0xc1/0xc6 age=99 cpu=0 pid=0
>> [   13.056366] INFO: Slab 0xffffea0000b0f9c0 objects=3 used=0
>> fp=0xffff88003290c090 flags=0x4000000000004082
>> [   13.056366] INFO: Object 0xffff88003290a048 @offset=8264
>> fp=0xffff880032908000
>> [   13.056366]
>> [   13.056366] Bytes b4 0xffff88003290a038:  b9 9e fb ff 00 00 00 00
>> 5a 5a 5a 5a 5a 5a 5a 5a ¹.ûÿ....ZZZZZZZZ
>
> Can you reproduce this? We had a similar report from Miles Lanes I
> have been trying to followup on for a while now. The suggested patches
> to try are:
>
> 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
>
>    Luis
>

as anticipated I had a feeling reproducing
this would be a bit of a challeng.

so far I was taking into account the actions that
I did yesterday to trigger this, but nothing i.e.

reboot 30 times(until fsck engages), and shutdown/start 30 times
with nothing of the sort.

If you have any ideas on how to reproduce this it would
be greatly appreciated(don't want to throw in the patches, until
I have something to go by).

on the other hand I could throw in the patches, and wait and see,
but would rather have more hard evidence that the patches do fix something.

Justin P. Mattock
--
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/