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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <201004252224.05509.pedrogfrancisco@gmail.com>
Date:	Sun, 25 Apr 2010 22:24:04 +0100
From:	Pedro Francisco <pedrogfrancisco@...il.com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	me@...copeland.com, 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?

A Domingo, 25 de Abril de 2010 21:29:45 Jiri Slaby escreveu:
> On 04/25/2010 09:22 PM, me@...copeland.com wrote:
> > 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.
> 
> These are CTS frames. So I think ath5k is to blame too :/.
> 
> regards,

Do note that's on a 2.6.32 kernel. I've however a new dmesg/syslog which on a 
2.6.34-rc5-daily has the same kind of issues. It's 400kB in size..... Do you 
want me to send it to the mailing list?

Or should I open a bug report on the kernel bugzilla and post them there? Or 
do both?

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