linux-kernel - Re: [PATCH 1/3] platform: x86: dell-rbtn: Dell Airplane Mode Switch driver

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]

Date:	Mon, 24 Nov 2014 21:50:26 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Pali Rohár <pali.rohar@...il.com>
Cc:	Darren Hart <dvhart@...radead.org>,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
	Gabriele Mazzotta <gabriele.mzt@...il.com>,
	Alex Hung <alex.hung@...onical.com>
Subject: Re: [PATCH 1/3] platform: x86: dell-rbtn: Dell Airplane Mode Switch
 driver

On Mon, Nov 24, 2014 at 09:55:47PM +0100, Pali Rohár wrote:

> This is complicated. HW switch controls all radio devices and you 
> do not know which are present in specified running machine. Also 
> list of devices which HW switch controls can be edited in BIOS 
> (on some machines). So what to do? We only know that it controls 
> some devices...

Typically there'll be a firmware method that provides a mask of the 
controlled devices. Do you have the ACPI tables for a device that 
implements this? Registering an rfkill interface that claims to only 
control wifi but which also kills other devices is likely to confuse 
userspace - it would probably be better to avoid registering the rfkill 
interface at all in that case.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/