From: Pavel Roskin <proski@gnu.org>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 12:48:42 -0400 [thread overview]
Message-ID: <1212252522.2766.8.camel@rd> (raw)
In-Reply-To: <69e28c910805310723j2b721030x2609cc9e866abafa@mail.gmail.com>
Hello!
You beat me at reporting it. I was about to report the same thing.
Basically, my laptop with bcm4311 started crashing when using WEP in th=
e
last weeks. Its runs the current wireless-testing.
On Sat, 2008-05-31 at 16:23 +0200, Stefanik G=E1bor wrote:
> #4 [c04619c8] b43_generate_txhdr at f8dd3a99
Yes, that's where it happens. This patch prevents the panic, but it's
almost certainly not the right fix.
diff --git a/drivers/net/wireless/b43/xmit.c
b/drivers/net/wireless/b43/xmit.c
index f9e1cff..5ec8d86 100644
--- a/drivers/net/wireless/b43/xmit.c
+++ b/drivers/net/wireless/b43/xmit.c
@@ -234,11 +234,14 @@ int b43_generate_txhdr(struct b43_wldev *dev,
=20
plcp_fragment_len =3D fragment_len + FCS_LEN;
if (use_encryption) {
- u8 key_idx =3D info->control.hw_key->hw_key_idx;
+ u8 key_idx;
struct b43_key *key;
int wlhdr_len;
size_t iv_len;
=20
+ if (!info->control.hw_key)
+ return -ENOKEY;
+ key_idx =3D info->control.hw_key->hw_key_idx;
B43_WARN_ON(key_idx >=3D dev->max_nr_keys);
key =3D &(dev->key[key_idx]);
=20
Another workaround is to use nohwcrypt=3D1 in the module options.
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).
I'm using 40-bit WEP with wpa_supplicant (because it's configured to
recognize many networks, some of which are with WPA). I don't know if
it's relevant. It's Fedora 9 for x86_64, but NetworkManager is
disabled.
--=20
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 12:48:42 -0400 [thread overview]
Message-ID: <1212252522.2766.8.camel@rd> (raw)
In-Reply-To: <69e28c910805310723j2b721030x2609cc9e866abafa@mail.gmail.com>
Hello!
You beat me at reporting it. I was about to report the same thing.
Basically, my laptop with bcm4311 started crashing when using WEP in the
last weeks. Its runs the current wireless-testing.
On Sat, 2008-05-31 at 16:23 +0200, Stefanik Gábor wrote:
> #4 [c04619c8] b43_generate_txhdr at f8dd3a99
Yes, that's where it happens. This patch prevents the panic, but it's
almost certainly not the right fix.
diff --git a/drivers/net/wireless/b43/xmit.c
b/drivers/net/wireless/b43/xmit.c
index f9e1cff..5ec8d86 100644
--- a/drivers/net/wireless/b43/xmit.c
+++ b/drivers/net/wireless/b43/xmit.c
@@ -234,11 +234,14 @@ int b43_generate_txhdr(struct b43_wldev *dev,
plcp_fragment_len = fragment_len + FCS_LEN;
if (use_encryption) {
- u8 key_idx = info->control.hw_key->hw_key_idx;
+ u8 key_idx;
struct b43_key *key;
int wlhdr_len;
size_t iv_len;
+ if (!info->control.hw_key)
+ return -ENOKEY;
+ key_idx = info->control.hw_key->hw_key_idx;
B43_WARN_ON(key_idx >= dev->max_nr_keys);
key = &(dev->key[key_idx]);
Another workaround is to use nohwcrypt=1 in the module options.
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).
I'm using 40-bit WEP with wpa_supplicant (because it's configured to
recognize many networks, some of which are with WPA). I don't know if
it's relevant. It's Fedora 9 for x86_64, but NetworkManager is
disabled.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-31 16:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 14:23 Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit Stefanik Gábor
2008-05-31 14:23 ` Stefanik Gábor
2008-05-31 15:11 ` Michael Buesch
2008-05-31 15:11 ` Michael Buesch
2008-05-31 16:34 ` Stefanik Gábor
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:50 ` Pavel Roskin
2008-05-31 16:50 ` Pavel Roskin
2008-05-31 17:54 ` Michael Buesch
2008-05-31 17:54 ` Michael Buesch
2008-05-31 20:22 ` Johannes Berg
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:48 ` Michael Buesch
2008-05-31 20:48 ` Michael Buesch
[not found] ` <20080602000841.qjrd66s3esgscko0-cebfxv@fcnzpbc.arg@webmail.spamcop.net>
2008-06-02 4:33 ` Pavel Roskin
2008-06-02 7:47 ` Johannes Berg
2008-05-31 16:48 ` Pavel Roskin [this message]
2008-05-31 16:48 ` Pavel Roskin
2008-05-31 16:54 ` Stefanik Gábor
2008-05-31 17:06 ` Pavel Roskin
2008-05-31 17:06 ` Pavel Roskin
2008-05-31 17:59 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1212252522.2766.8.camel@rd \
--to=proski@gnu.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.