linux-kernel - Re: iwl3945 dies (oops) in post 2.6.34 kernels

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:	Tue, 25 May 2010 12:55:24 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	linux-wireless@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: iwl3945 dies (oops) in post 2.6.34 kernels

On Tue, May 25, 2010 at 09:39:20AM -0700, Dmitry Torokhov wrote:
> Hi,
> 
> I am getting the following crashers in iwl3945 after updating to
> post-2.6.34 kernels. This is with the pull from Linus's tree as of last
> night (the taint is from nvidia module):

Linus doesn't have this one yet:

commit 073d5eab6fc85b6c278d507a5633b759a85dc878
Author: Reinette Chatre <reinette.chatre@...el.com>
Date:   Thu May 13 14:49:44 2010 -0700

    iwlwifi: fix internal scan race
    
    It is possible for internal scan to race against itself if the device is
    not returning the scan results from first requests. What happens in this
    case is the cleanup done during the abort of the first internal scan also
    cleans up part of the new scan, causing it to access memory it shouldn't.
...

I suspect it might be related.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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/