linux-kernel - Re: ath9k: panic on tip/master

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:	Fri, 3 Oct 2008 12:02:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Noonan <steven@...inklabs.net>
Cc:	linux-kernel@...r.kernel.org, ath9k-devel@...ts.ath9k.org,
	lrodriguez@...eros.com
Subject: Re: ath9k: panic on tip/master

* Steven Noonan <steven@...inklabs.net> wrote:

> Hey folks,
> 
> Just got a panic on tip. According to the stack trace, ath9k is what 
> decided to bomb.
> 
> http://www.uplinklabs.net/~tycho/linux/ath9k_panic_tip_10.3.2008.jpg
> 
> Note: Although it says 'sudo modprobe radeon' on the bash prompt above 
> the panic, I never got to hit 'enter' on that command before the panic 
> occurred.

it appears to me that ath9k's eth_rx_input() takes a spinlock that is 
not initialized (or already destroyed by the allocator).

this would be consistent with an IRQ storm hitting some race in the 
ath9k driver init sequence. For example if request_irq() is done before 
all structures that the IRQ handler relies on are properly initialized.

i.e. this has the signature of a genuine ath9k bug.

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