summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2012-10-26 16:04:08 -0400
committerJ. Bruce Fields <bfields@redhat.com>2012-11-07 19:31:33 -0500
commitfae5096ad217db2e3368e980c1d86223f786856b (patch)
treeefe6c90695ee97eb12364ff7756821a67ccc9f7a /init
parent7fa10cd12df3ec0873a5db0d8dc8e978423b87dc (diff)
downloadop-kernel-dev-fae5096ad217db2e3368e980c1d86223f786856b.zip
op-kernel-dev-fae5096ad217db2e3368e980c1d86223f786856b.tar.gz
nfsd: assume writeable exportabled filesystems have f_sync
I don't really see how you could claim to support nfsd and not support fsync somehow. And in practice a quick look through the exportable filesystems suggests the only ones without an ->fsync are read-only (efs, isofs, squashfs) or in-memory (shmem). Also, performing a write and then returning an error if the sync fails (as we would do here in the wgather case) seems unhelpful to clients. Also remove an incorrect comment. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud