From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath9k-devel@venema.h4ckr.net
Subject: Re: [ath9k-devel] BUG kmalloc-8192: Poison overwritten
Date: Wed, 02 Dec 2009 15:28:34 -0800 [thread overview]
Message-ID: <4B16F822.9050807@gmail.com> (raw)
In-Reply-To: <43e72e890912021516k736db118j217dc92496db8f19@mail.gmail.com>
On 12/02/09 15:16, Luis R. Rodriguez wrote:
> On Wed, Dec 2, 2009 at 2:27 PM, Justin Mattock<justinmattock@gmail.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
>
just noticed the other thread.
I can tryout these patches and see.
As for reproducing this, tough to say...
during my looking into udev I was rebooting
a few times(maybe 10/15) then hit this.
I'll try and reproduce this,before using these
patches so I can verify they take care of the issue.
(but could be difficult to reproduce);
Justin P. Mattock
next prev parent reply other threads:[~2009-12-02 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 22:27 BUG kmalloc-8192: Poison overwritten Justin Mattock
2009-12-02 23:16 ` [ath9k-devel] " Luis R. Rodriguez
2009-12-02 23:28 ` Justin P. Mattock [this message]
2009-12-03 21:36 ` Justin P. Mattock
2009-12-03 21:45 ` Luis R. Rodriguez
2009-12-03 21:58 ` Justin P. Mattock
2009-12-04 5:22 ` Justin P. 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=4B16F822.9050807@gmail.com \
--to=justinmattock@gmail.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@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