netdev - Re: rfkill-input to be removed

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]

Message-ID: <1303402951.3597.27.camel@jlt3.sipsolutions.net>
Date:	Thu, 21 Apr 2011 18:22:31 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Marco Chiappero <marco@...ence.it>
Cc:	netdev@...r.kernel.org
Subject: Re: rfkill-input to be removed

On Thu, 2011-04-21 at 10:28 +0200, Marco Chiappero wrote:
> While working on the the sony-laptop driver, adding support for 
> persistent rfkill state storing and adding the SW_RFKILL_ALL switch 
> event forwarding to the input core to notify userspace, I realized that 
> rfkill-input interferes with correct behavior of the driver, vanishing 
> the hardware device state storing. 

Yeah we noticed this before with some other drivers. The persistent
stuff seems to only be suitable for a small number of semantics.

> Then, looking at 
> Documentation/feature-removal-schedule.txt I realized that rfkill-input 
> was scheduled to be removed in 2.6.33, but it's still there in 2.6.39. 
> Please remove that code as soon as possible, rfkill input events should 
> be handled by user space tools.

Frankly, I don't think we're ready for this yet, most distros don't yet
ship the rfkill daemon.

johannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html