* 2.6.24 - self-destructing sysfs attributes
@ 2007-10-30 19:23 Andrey Borzenkov
0 siblings, 0 replies; only message in thread
From: Andrey Borzenkov @ 2007-10-30 19:23 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
I realized that in patch for ACPI battery I created perfect example of
self-destructing sysfs attributes. Basically, on every access to battery
properties we check battery status. If ACPI reports battery not present, we
remove sysfs power_supply object. I.e.
-> user space queries e.g. .../PNP0C0A:00/power_supply/BAT1/energy_now
-> call acpi_battery_update
-> battery gone
-> call power_supply_unregister(.../PNP0C0A:00/power_supply)
I remember discussion about this but am not sure what final outcome is. So
questions
- is it legal in this form?
- what is the proper way to manage such situation?
- if I move (de-)registering of power_supply out of acpi_battery_update, is
extra locking (refcounting) required to keep attributes alive or sysfs will
ensure this?
TIA
-andrey
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-10-30 19:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-30 19:23 2.6.24 - self-destructing sysfs attributes Andrey Borzenkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome