linux-kernel - Re: Bcm43xx softMac Driver in 2.6.18

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

Message-ID: <451D8EB4.6020000@madrabbit.org>
Date:	Fri, 29 Sep 2006 14:23:00 -0700
From:	Ray Lee <ray-lk@...rabbit.org>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, dbtsai@...il.com,
	John Linville <linville@...driver.com>, netdev@...r.kernel.org,
	Bcm43xx-dev@...ts.berlios.de, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Bcm43xx softMac Driver in 2.6.18

(re-adding linux-kernel.)

Larry Finger wrote:
> Would you please test the attached patch that should be applied to a
> vanilla 2.6.18? I'm currently running it, but only for a few minutes. It
> comes up fine and I ran it through several ifdown/ifup cycles without
> any problem.

Okay, this is far better than vanilla 2.6.18 (or your other patch). I've
been running this for six hours so far with no troubles, when before I'd
have a hard system freeze within a minute or two of associating (or
trying to associate) with an access point.

As for -stable, the patch is sorta, y'know, ginormous:

 bcm43xx.h         |  181 +++++-----
 bcm43xx_debugfs.c |   80 ++++
 bcm43xx_debugfs.h |    1
 bcm43xx_dma.c     |  583 +++++++++++++++++++++++-----------
 bcm43xx_dma.h     |  296 +++++++++++++----
 bcm43xx_leds.c    |   10
 bcm43xx_main.c    |  905
+++++++++++++++++++++++++++++++-----------------------
 bcm43xx_main.h    |    6
 bcm43xx_phy.c     |   48 +-
 bcm43xx_pio.c     |    4
 bcm43xx_sysfs.c   |   46 +-
 bcm43xx_wx.c      |  121 +++----
 12 files changed, 1426 insertions(+), 855 deletions(-)

OTOH, the current version is completely unusable on this system, so I
don't know if the right path is to revert the driver to 2.6.17's
version, or to try to move forward with the patch when it's had hard
review and testing.

I'm heading out on vacation for the next two weeks. I'll catch up with
any mail directed to me for more things to try (or report about this
specific system), if requested, when I get back. (Or catch me today.)

Thank you very much for your help,

Ray
-
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/