Skip to content

Commit

Permalink
ovl: Sync upper dirty data when syncing overlayfs
Browse files Browse the repository at this point in the history
commit e8d4bfe upstream.

When executing filesystem sync or umount on overlayfs,
dirty data does not get synced as expected on upper filesystem.
This patch fixes sync filesystem method to keep data consistency
for overlayfs.

Signed-off-by: Chengguang Xu <cgxu@mykernel.net>
Fixes: e593b2b ("ovl: properly implement sync_filesystem()")
Cc: <stable@vger.kernel.org> #4.11
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  • Loading branch information
Chengguang Xu authored and gregkh committed Aug 3, 2018
1 parent 21b5b5e commit 6aaaca7
Showing 1 changed file with 15 additions and 4 deletions.
19 changes: 15 additions & 4 deletions fs/overlayfs/super.c
Original file line number Diff line number Diff line change
Expand Up @@ -232,6 +232,7 @@ static void ovl_put_super(struct super_block *sb)
kfree(ufs);
}

/* Sync real dirty inodes in upper filesystem (if it exists) */
static int ovl_sync_fs(struct super_block *sb, int wait)
{
struct ovl_fs *ufs = sb->s_fs_info;
Expand All @@ -240,14 +241,24 @@ static int ovl_sync_fs(struct super_block *sb, int wait)

if (!ufs->upper_mnt)
return 0;
upper_sb = ufs->upper_mnt->mnt_sb;
if (!upper_sb->s_op->sync_fs)

/*
* If this is a sync(2) call or an emergency sync, all the super blocks
* will be iterated, including upper_sb, so no need to do anything.
*
* If this is a syncfs(2) call, then we do need to call
* sync_filesystem() on upper_sb, but enough if we do it when being
* called with wait == 1.
*/
if (!wait)
return 0;

/* real inodes have already been synced by sync_filesystem(ovl_sb) */
upper_sb = ufs->upper_mnt->mnt_sb;

down_read(&upper_sb->s_umount);
ret = upper_sb->s_op->sync_fs(upper_sb, wait);
ret = sync_filesystem(upper_sb);
up_read(&upper_sb->s_umount);

return ret;
}

Expand Down

0 comments on commit 6aaaca7

Please sign in to comment.