linux-kernel - Re: eeepc-laptop rfkill, stupid question #4

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 Nov 2008 14:33:11 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Alan Jenkins <alan-jenkins@...fmail.co.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux acpi <linux-acpi@...r.kernel.org>
Subject: Re: eeepc-laptop rfkill, stupid question #4

On Mon, 03 Nov 2008, Matthew Garrett wrote:
> On Mon, Nov 03, 2008 at 01:02:29PM -0200, Henrique de Moraes Holschuh wrote:
> > Right now, you should still rfkill_force_state().  Please wait for an hour
> > or two while I clean up that broken resume handling, and I will tell you for
> > sure.
> 
> Cool. I'll hold off posting my cleanups until then in that case.

Ok, two bugs reproduced, the fixes are ready and tested, and I will be
sending it now to linux-wireless.  You're in the CC, so you will get them.

I will also need to send patches for -stable, as the ones for mainline won't
apply to -stable.

Now, for what you asked: you DO NOT HAVE to use rfkill_force_state() in your
driver's resume method, as long as you NEVER make use of
RFKILL_STATE_HARD_BLOCKED.   I have fixed the bug that was messing this up.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/