linux-kernel - Re: ath5k gets lost with eeepc-laptop removal

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: <40f31dec0810311135w76c01729lef1a6c93f18c0095@mail.gmail.com>
Date:	Fri, 31 Oct 2008 20:35:47 +0200
From:	"Nick Kossifidis" <mickflemm@...il.com>
To:	"Matthew Garrett" <mjg59@...f.ucam.org>
Cc:	"Alan Jenkins" <alan-jenkins@...fmail.co.uk>,
	"Luiz Fernando N. Capitulino" <lcapitulino@...driva.com.br>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	willy@...ux.intel.com, lrodriguez@...eros.com
Subject: Re: ath5k gets lost with eeepc-laptop removal

2008/10/31 Matthew Garrett <mjg59@...f.ucam.org>:
> On Fri, Oct 31, 2008 at 01:51:49PM +0000, Alan Jenkins wrote:
>
>> Matthew: I nagged you twice about different consequences of this
>> commit, so here's a third :).  You said rfkill no longer automatically
>> frobs on suspend/resume, which was what I was worried about last time.
>> Should the core code also be modified so it doesn't do anything when
>> the rfkill device is unregistered?
>
> I think there's definitely an argument in favour of that, though I
> suspect that's a design feature - if you remove the control mechanism
> for a radio, the safe state for that radio to be in is not transmitting.
>

It doesn't leave the radio in a state that's not transmitting, it
leaves the card in a state that doesn't get any power at all. I don't
see any reason for this, how do you define "safe" ?



-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
--
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/