linux-kernel - Re: iwlagn: wrong command queue backtrace.

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] [day] [month] [year] [list]

Message-ID: <CANUX_P01gBqCX1XNydm=pZQMmSgUsg1D4uUx9ngeFdY8YoALDA@mail.gmail.com>
Date:	Thu, 9 Feb 2012 09:19:39 +0200
From:	Emmanuel Grumbach <egrumbach@...il.com>
To:	Daniel Halperin <dhalperi@...washington.edu>
Cc:	Dave Jones <davej@...hat.com>,
	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>,
	linux-kernel@...r.kernel.org, ipw3945-devel@...ts.sourceforge.net,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>
Subject: Re: iwlagn: wrong command queue backtrace.

>>
>> I just hit this with the iwlagn driver currently in Linus' tree.
>>
>
> AFAICT this could be a side effect of some bad QoS packet processing.
> The patch (http://www.spinics.net/lists/linux-wireless/msg84213.html)
> hasn't yet made it to Linus' tree, but you could cherry-pick it...
>

Although I would like to believe it is related, I don't think it is.
The question is how reproducible this bug is.

This badly looks like your report from around 3 months:

https://lkml.org/lkml/2011/11/25/60
--
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/