Toward a safer sysfs
Posted Apr 12, 2007 2:58 UTC (Thu) by flewellyn
Parent article: Toward a safer sysfs
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"?
to post comments)