mirror of
https://github.com/torvalds/linux.git
synced 2024-11-10 22:21:40 +00:00
sysfs.txt: mention that store method buffers are null-terminated
Without knowing this, the use of sysfs_streq() becomes puzzling. The termination happens in kernfs_fop_write(). Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com> [jc: moved the new text to a different paragraph] Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
9ba41327d8
commit
17666497fe
@ -191,9 +191,10 @@ implementations:
|
|||||||
be called again, rearmed, to fill the buffer.
|
be called again, rearmed, to fill the buffer.
|
||||||
|
|
||||||
- On write(2), sysfs expects the entire buffer to be passed during the
|
- On write(2), sysfs expects the entire buffer to be passed during the
|
||||||
first write. Sysfs then passes the entire buffer to the store()
|
first write. Sysfs then passes the entire buffer to the store() method.
|
||||||
method.
|
A terminating null is added after the data on stores. This makes
|
||||||
|
functions like sysfs_streq() safe to use.
|
||||||
|
|
||||||
When writing sysfs files, userspace processes should first read the
|
When writing sysfs files, userspace processes should first read the
|
||||||
entire file, modify the values it wishes to change, then write the
|
entire file, modify the values it wishes to change, then write the
|
||||||
entire buffer back.
|
entire buffer back.
|
||||||
|
Loading…
Reference in New Issue
Block a user