2424b5dd06
Requiring userspace to close and re-open sysfs attributes has been the policy since before 2.6.12. It allows userspace to get a consistent snapshot of kernel state and consume it with incremental reads and seeks. Now, if the file position is zero the kernel assumes userspace wants to see the new value. The application for this change is to allow a userspace RAID metadata handler to check the state of an array without causing any memory allocations. Thus not causing writeback to a raid array that might be blocked waiting for userspace to take action. Cc: Neil Brown <neilb@suse.de> Acked-by: Tejun Heo <htejun@gmail.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> |
||
|---|---|---|
| .. | ||
| configfs | ||
| 9p.txt | ||
| 00-INDEX | ||
| adfs.txt | ||
| affs.txt | ||
| afs.txt | ||
| automount-support.txt | ||
| befs.txt | ||
| bfs.txt | ||
| cifs.txt | ||
| coda.txt | ||
| cramfs.txt | ||
| dentry-locking.txt | ||
| directory-locking | ||
| dlmfs.txt | ||
| dnotify.txt | ||
| ecryptfs.txt | ||
| Exporting | ||
| ext2.txt | ||
| ext3.txt | ||
| ext4.txt | ||
| files.txt | ||
| fuse.txt | ||
| gfs2.txt | ||
| hfs.txt | ||
| hfsplus.txt | ||
| hpfs.txt | ||
| inotify.txt | ||
| isofs.txt | ||
| jfs.txt | ||
| Locking | ||
| locks.txt | ||
| mandatory-locking.txt | ||
| ncpfs.txt | ||
| nfsroot.txt | ||
| ntfs.txt | ||
| ocfs2.txt | ||
| porting | ||
| proc.txt | ||
| quota.txt | ||
| ramfs-rootfs-initramfs.txt | ||
| relay.txt | ||
| romfs.txt | ||
| rpc-cache.txt | ||
| seq_file.txt | ||
| sharedsubtree.txt | ||
| smbfs.txt | ||
| spufs.txt | ||
| sysfs-pci.txt | ||
| sysfs.txt | ||
| sysv-fs.txt | ||
| tmpfs.txt | ||
| udf.txt | ||
| ufs.txt | ||
| vfat.txt | ||
| vfs.txt | ||
| xfs.txt | ||
| xip.txt | ||