On Wed, 05 Apr 2006 16:39:57 BST, Al Viro said: > How about _NOT_ using sysfs and just having ->read()/->write() on a file in fs > of your own? ~20 lines for all of it, not counting #include... Great. Instead of everybody using the same piece-of-manure sysfs interface, each driver carries around its 20 lines to implement read() and write() in subtly buggy and incompatible ways. % grep nodev /proc/filesystems | wc -l 19 That's fsck'ing insane already.
Attachment:
pgphsIQ0PK8Ep.pgp
Description: PGP signature
- Follow-Ups:
- References:
- [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- From: [email protected]
- Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- From: Sergey Vlasov <[email protected]>
- Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- From: Al Viro <[email protected]>
- Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- From: "Jon Smirl" <[email protected]>
- Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- From: Al Viro <[email protected]>
- [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- Prev by Date: Re: [PATCH 7/7] tpm: Driver for next generation TPM chips
- Next by Date: bug-report (kernel-oops)
- Previous by thread: Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- Next by thread: Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
- Index(es):
 |