linux-kernel - Re: REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's

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]

Message-Id: <20111221.161607.1331587831465613240.davem@davemloft.net>
Date:	Wed, 21 Dec 2011 16:16:07 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	tytso@....edu
Cc:	johannes@...solutions.net, linux-kernel@...r.kernel.org,
	ilw@...ux.intel.com, linux-wireless@...r.kernel.org
Subject: Re: REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's

From: "Ted Ts'o" <tytso@....edu>
Date: Wed, 21 Dec 2011 16:12:13 -0500

> On Tue, Dec 13, 2011 at 08:59:59PM -0500, Ted Ts'o wrote:
>> On Tue, Dec 13, 2011 at 03:17:52PM -0500, Ted Ts'o wrote:
>> ... and the second problem I had with associating with EAP-TLS
>> encrypted SSID's was solved by Wey-Yi's patch: 
>> 
>> 	  iwlwifi: allow to switch to HT40 if not associated yet
>> 
>> ... found in the thread "iwlagn regression in v3.1.5"
>> 
>> So with these two patches applied, things are now stable for me.
> 
> It seems that fixes for these two issues haven't been pushed to Linus
> yet?  It would be nice if they could get pushed to mainline before 3.2
> ships, as opposed to being something that has to get fixed in the
> 3.2.X series....

It's in my queue to send to Linus.
--
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/