linux-kernel - Re: Wireless-testing's b43 panics in b43_generate

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: <1212253604.2766.15.camel@rd>
Date:	Sat, 31 May 2008 13:06:44 -0400
From:	Pavel Roskin <proski@....org>
To:	Stefanik Gábor <netrolller.3d@...il.com>
Cc:	"bcm43xx-dev@...ts.berlios.de" <bcm43xx-dev@...ts.berlios.de>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet
	transmit

On Sat, 2008-05-31 at 18:54 +0200, Stefanik Gábor wrote:
> On Sat, May 31, 2008 at 6:48 PM, Pavel Roskin <proski@....org> wrote:
> > It's strange that other drivers (b43legacy, ath5k) use
> > info->control.hw_key->hw_key_idx under the same conditions (see how
> > use_encryption is calculated), but don't have any problems on the same
> > network (but I need to recheck).
> 
> Hmm... does ath5k use hardware crypto?

No, it doesn't, at least with WEP, if I understand ath5k_set_key()
correctly.

> B43 does (but not with
> nohwcrypt - and that appears to be a valid workaround), b43legacy
> doesn't AFAIK.

Although the code with use_encryption is present in b43legacy, it don't
see any references to "set_key", so I guess you are right.

Well, that explains something.

-- 
Regards,
Pavel Roskin
--
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/