linux-kernel - Re: [ath5k-devel] [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:	Mon, 2 Mar 2009 12:34:18 -0500
From:	Bob Copeland <me@...copeland.com>
To:	Sitsofe Wheeler <sitsofe@...oo.com>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	ath5k-devel@...ema.h4ckr.net
Subject: Re: [ath5k-devel] [TIP] BUG kmalloc-4096: Poison overwritten 
	(ath5k_rx_skb_alloc)

On Thu, Feb 26, 2009 at 12:03 PM, Sitsofe Wheeler <sitsofe@...oo.com> wrote:
> On Thu, Feb 26, 2009 at 08:59:39AM -0500, Bob Copeland wrote:
>> On Wed, Feb 25, 2009 at 02:01:39PM +0000, Sitsofe Wheeler wrote:
>> > It has been days since the original BUG occurred and further it
>> > originally had happened in a -tip kernel with kmemcheck compiled into
>> > it. I had been utterly unable to reproduce the error on any network with
>> > a stock 2.6.29-rc6 kernel. Not even the original -tip kernel produced
>> > the error again...
>
> Note that I was able to reproduce it again : )

So, I took this config and tried a few things without success:

 - turned on failslab fault injection
 - added various mdelay()s to try to widen theoretical race conditions
 - generated traffic with iperf and 'iwlist wlan0 scan' (as root in a loop)

At this point, I think ftrace is the way to go.  I guess a good start
would be the functions in:

grep 'ath5k' available_filter_functions | \
    egrep -v '(debug)|(eeprom)|(hw)|(intr)'

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