linux-kernel - Re: ath5k misbehaving affecting other kernel parts unrelated?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100425192242.GA27921@hash.localnet>
Date:	Sun, 25 Apr 2010 15:22:42 -0400
From:	me@...copeland.com
To:	Pedro Francisco <pedrogfrancisco@...il.com>
Cc:	Vegard Nossum <vegard.nossum@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	mickflemm@...il.com
Subject: Re: ath5k misbehaving affecting other kernel parts unrelated?

On Sat, Apr 24, 2010 at 06:28:36PM +0100, Pedro Francisco wrote:
> =============================================================================
> [ 2658.663424] BUG kmalloc-4096: Poison overwritten
> [ 2658.663483] 

Ok there are 4 messages here, two of them are definitely 802.11 beacons,
which would point the finger squarely at ath5k.  We had reports of this
some time ago but a few things got rewritten around that time.  I'd guess
the rx DMA code is still subtly broken. 

> 6b 6b kkkkkkkkkkkkkkkk
> [ 2658.664816]   Object 0xed3db0c0:  c4 00 84 00 00 22 43 89 42 69 4e 12 ca 6f 
> 6f 6f �...."C.BiN.�ooo
> [ 4689.945547]   Object 0xed3d9080:  c4 00 70 00 00 22 43 89 42 69 fe 08 eb 14 
> 14 14 �.p.."C.Bi�.�...

Offhand, I'm not sure what pattern these are.

> [14487.165341]   Object 0xed378040:  80 00 00 00 ff ff ff ff ff ff 00 1e 8c 0f 3e af 
> [24370.460011]   Object 0xed3dc100:  80 00 00 00 ff ff ff ff ff ff 00 1e 8c 0f 3e af 

These two are definitely beacons.

-- 
Bob Copeland %% www.bobcopeland.com

--
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/