On Wed, 27 Jun 2007, Michael Buesch wrote: > Ok, all very good ideas. Patches are welcome ;)
Not from me, sorry. I really don't have the time, or the drive, to do it right now. thinkpad-acpi is taking all my "kernel code" time, which is not much. > > I don't much like sysfs over IOCTLs for this, as you will probably need to > > be able to set and get things in an atomic way. A sysfs binary attribute > > would also work. A sysfs one-value-per-attribute bunch of them is > > completely useless from a security point of view. > > hm? Why? Because you cannot risk anyone changing one of them behind your back while you are trying to set them all before you lock them. And I am not even considering an attack scenario, I am considering two apps trying to set it up concurrently. You need some sort of locking for this sort of device, and exclusive open + ioctl solves the problem completely. Sysfs is not made for this kind of thing. -- "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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
