ovl: fix failure to fsync lower dir

As a writable mount, it is not expected for overlayfs to return
EINVAL/EROFS for fsync, even if dir/file is not changed.

This commit fixes the case of fsync of directory, which is easier to
address, because overlayfs already implements fsync file operation for
directories.

The problem reported by Raphael is that new PostgreSQL 10.0 with a
database in overlayfs where lower layer in squashfs fails to start.
The failure is due to fsync error, when PostgreSQL does fsync on all
existing db directories on startup and a specific directory exists
lower layer with no changes.

Reported-by: Raphael Hertzog <[email protected]>
Cc: <[email protected]> # v3.18
Signed-off-by: Amir Goldstein <[email protected]>
Tested-by: Raphaël Hertzog <[email protected]>
Signed-off-by: Miklos Szeredi <[email protected]>

0 files changed, 0 insertions, 0 deletions