linux-kernel - rfkill vs. HAL, 2.6.27-rc3

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]

Date:	Wed, 13 Aug 2008 02:53:35 -0400
From:	Jim Paris <jim@...n.com>
To:	ibm-acpi-devel@...ts.sourceforge.net
Cc:	linux-kernel@...r.kernel.org
Subject: rfkill vs. HAL, 2.6.27-rc3

On my Thinkpad X61, I have lots of problems on 2.6.26.1 when toggling
rfkill switches and buttons, including kernel crashes, so I'm trying
out 2.6.27-rc3.  Rfkill seems much better behaved, but Network-manager
is not very happy with it and no longer notices when the radio is
killed.

I think this is because it uses the HAL killswitch interface
  org.freedesktop.Hal.Device.KillSwitch
which calls the script
  hal-system-killswitch-get-power
which calls
  hal-system-killswitch-get-power-linux
which uses the binary
  hal-ipw-killswitch-linux
to check
  /sys/class/net/wlan0/device/rf_kill.

But this file no longer exists.  It seems to have been renamed to 
"/sys/class/net/wlan0/device/rfkill:rfkill2", which is extra annoying
because it's not just a rename, now hal-ipw-killswitch-linux will have
to find the "rfkill2" suffix.

Seems like a kernel regression if upgrading breaks user applications.
Or does this sound like a HAL bug?  Or Network-manager?  Or..?

(tracking a single bit of state is getting way too complex these
days...)

-jim
--
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/