linux-kernel - Re: Linux 2.6.32-rc5 - eeepc-laptop/rt2860 panic fix patches

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: <mpro.krm886004sbpc026m.linux@youmustbejoking.demon.co.uk>
Date:	Fri, 16 Oct 2009 17:24:06 +0100
From:	Darren Salt <linux@...mustbejoking.demon.co.uk>
To:	linux-kernel@...r.kernel.org
Cc:	torvalds@...ux-foundation.org
Subject: Re: Linux 2.6.32-rc5 - eeepc-laptop/rt2860 panic fix patches

I demand that Linus Torvalds may or may not hae written...

> Darren Salt (2):
>      eeepc-laptop: Prevent a panic when disabling RT2860 wireless when
>        associated

This patch (commit b56ab33d68638e6aafdbfc694025e8354a628f49) causes problems
with at least some alternative hardware, and should be reverted. I found that
if I substitute an Intel 3945 for the RT2860 in my 901 then, when eeepc-wlan
is toggled, we get rfkill set → eeepc-laptop → iwl3945 → rfkill remove (and
one process stuck in state D), and if I flip the flag which causes this, that
works fine but rt2860sta will happily cause a panic again.

Both I and Corentin Chary have unsuccessfully tried to get this patch
dropped.

>      Staging: rt2860sta: prevent a panic when disabling when associated

It has been superseded by this patch (commit
0af49167b1e5ba154e90d2c454bf4624ee47df80).

-- 
| Darren Salt            | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds    ,demon,co,uk    | Northumberland | Army
| + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING.

I know a good tagline when I steal one.
--
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/