LWN: Comments on "Toward a safer sysfs"

Toward a safer sysfs

jd — Thu, 19 Apr 2007 18:55:05 +0000

Does that mean a device driver to make weasels erupt from a user's
nostrils will be broken? Can we add a special API for such drivers, say
next April 1st?

Toward a safer sysfs

corbet — Thu, 12 Apr 2007 03:09:15 +0000

Exactly that - it returns ENODEV.

Toward a safer sysfs

flewellyn — Thu, 12 Apr 2007 02:58:22 +0000

Okay, so what DOES happen when you try to read from, or write to, a sysfs file for which the
device no longer exists?

I mean, obviously this new code will prevent the system from causing weasels to erupt from your
nostrils or whatever other catastrophic event might occur, but surely there should be some
defined behavior here? Something along the lines of "device no longer exists, go away"?