User: Password:
Subscribe / Log in / New account

Toward a safer sysfs

Toward a safer sysfs

Posted Apr 12, 2007 2:58 UTC (Thu) by flewellyn (subscriber, #5047)
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"?

(Log in to post comments)

Toward a safer sysfs

Posted Apr 12, 2007 3:09 UTC (Thu) by corbet (editor, #1) [Link]

Exactly that - it returns ENODEV.

Toward a safer sysfs

Posted Apr 19, 2007 18:55 UTC (Thu) by jd (guest, #26381) [Link]

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?

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds