aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/os/fileio.c
diff options
context:
space:
mode:
authorJustin M. Keyes <justinkz@gmail.com>2019-02-20 21:52:12 +0100
committerJustin M. Keyes <justinkz@gmail.com>2019-02-21 02:00:51 +0100
commit996916277d9845b61f026c53197880889e5004e2 (patch)
treed9c16d4750dc98b8af6109faf3283e254b6a119f /src/nvim/os/fileio.c
parentc59aa771a631be53215eaadadfa4589d168a5c2b (diff)
downloadrneovim-996916277d9845b61f026c53197880889e5004e2.tar.gz
rneovim-996916277d9845b61f026c53197880889e5004e2.tar.bz2
rneovim-996916277d9845b61f026c53197880889e5004e2.zip
I/O: ignore ENOTSUP for failed fsync()
Suggested by ZyX in https://github.com/neovim/neovim/issues/6725#issuecomment-312197691 : > There already is an exception if writing to a “device” (e.g. FIFO). > It makes sense to ignore certain errors like ENOTSUP or EOPNOTSUPP > since it is not something we or user can do anything about. ref #6725
Diffstat (limited to 'src/nvim/os/fileio.c')
-rw-r--r--src/nvim/os/fileio.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/nvim/os/fileio.c b/src/nvim/os/fileio.c
index ccf35fd57c..bb68326a03 100644
--- a/src/nvim/os/fileio.c
+++ b/src/nvim/os/fileio.c
@@ -229,7 +229,10 @@ int file_fsync(FileDescriptor *const fp)
return flush_error;
}
const int fsync_error = os_fsync(fp->fd);
- if (fsync_error != UV_EINVAL && fsync_error != UV_EROFS) {
+ if (fsync_error != UV_EINVAL
+ && fsync_error != UV_EROFS
+ // fsync not supported on this storage.
+ && fsync_error != UV_ENOTSUP) {
return fsync_error;
}
return 0;