linux-kernel - Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb

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]

Date:	Sun, 29 Mar 2009 15:24:32 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Bob Copeland <me@...copeland.com>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	Nick Kossifidis <mickflemm@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	ath5k-devel@...ema.h4ckr.net,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Subject: Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)

On Fri, Mar 20, 2009 at 09:14:37AM -0400, Bob Copeland wrote:
> 
> Looks like the skb was reused right after it was freed by the mac80211
> workqueue so that seems inline with the idea that the list is getting
> corrupted somehow.  On top of the last patch, would you mind running 
> this overnight?  It'll dump a lot of debug info, I'm really only 
> interested in the last 5 invocations of ath5k_debug_printrxbuffs or so
> before the poison.  During a scan you'll see lots of rx_start/rx_stop.

I've been away travelling for the past week and I move house on the 1st
April (which will make testing this much harder from then on) but I'll
try to get one final test in before the move.

Do you need an ftrace in addition to dmesg for this? If so is it better
to leave ieee calls out of the ftrace?

-- 
Sitsofe | http://sucs.org/~sits/
--
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/