summaryrefslogtreecommitdiffstats
path: root/fs/kernfs/file.c
diff options
context:
space:
mode:
authorTony Luck <tony.luck@intel.com>2016-10-14 10:56:42 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-10-27 17:47:11 +0200
commit2a9becdd4dbed499815938308bdab9aae70dd561 (patch)
tree4dd2519edf64288329c6f00b3c20f7dca9fa0593 /fs/kernfs/file.c
parent07d9a380680d1c0eb51ef87ff2eab5c994949e69 (diff)
downloadtalos-op-linux-2a9becdd4dbed499815938308bdab9aae70dd561.tar.gz
talos-op-linux-2a9becdd4dbed499815938308bdab9aae70dd561.zip
kernfs: Add noop_fsync to supported kernfs_file_fops
If you edit a kernfs backed file with vi(1), you see an ugly error message when you write the file because vi tries to fsync(2) the file after writing, which fails. We have noop_fsync() for this, use it. Signed-off-by: Tony Luck <tony.luck@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/kernfs/file.c')
-rw-r--r--fs/kernfs/file.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/kernfs/file.c b/fs/kernfs/file.c
index 2bcb86e6e6ca..78219d5644e9 100644
--- a/fs/kernfs/file.c
+++ b/fs/kernfs/file.c
@@ -911,6 +911,7 @@ const struct file_operations kernfs_file_fops = {
.open = kernfs_fop_open,
.release = kernfs_fop_release,
.poll = kernfs_fop_poll,
+ .fsync = noop_fsync,
};
/**
OpenPOWER on IntegriCloud