linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-unionfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] overlayfs: fix ro/rw fd data inconsistecies
Date: Thu, 24 Nov 2016 11:55:37 +0100	[thread overview]
Message-ID: <1479984944-1017-2-git-send-email-mszeredi@redhat.com> (raw)
In-Reply-To: <1479984944-1017-1-git-send-email-mszeredi@redhat.com>

A file is opened for read-only, opened read-write (resulting in a copy up)
and modified.  The data read back from the the read-only fd will be stale
in this case (the read-only file descriptor still refers to the lower,
unmodified file).

This patchset fixes issues related to this corner case.

The VFS impact is minimal and performance in the non-corner cases shouldn't
suffer.
---
Miklos Szeredi (7):
  vfs: allow overlayfs to intercept file ops
  vfs: export filp_clone_open()
  mm: ovl: copy-up on MAP_SHARED
  ovl: add infrastructure for intercepting file ops
  ovl: intercept read_iter
  ovl: intercept mmap
  ovl: intercept fsync

 fs/internal.h            |   1 -
 fs/open.c                |   2 +-
 fs/overlayfs/inode.c     | 225 +++++++++++++++++++++++++++++++++++++++++++++++
 fs/overlayfs/overlayfs.h |   2 +
 fs/overlayfs/super.c     |   1 +
 include/linux/fs.h       |   1 +
 mm/util.c                |  22 +++++
 7 files changed, 252 insertions(+), 2 deletions(-)

-- 
2.5.5


  reply	other threads:[~2016-11-24 10:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 10:55 [PATCH 0/7] overlayfs: fix ro/rw fd data inconsistecies Miklos Szeredi
2016-11-24 10:55 ` Miklos Szeredi [this message]
2016-11-24 14:14   ` Miklos Szeredi
2016-11-24 20:50     ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 1/7] vfs: allow overlayfs to intercept file ops Miklos Szeredi
2016-11-24 10:55 ` [PATCH 2/7] vfs: export filp_clone_open() Miklos Szeredi
2016-11-24 10:55 ` [PATCH 3/7] mm: ovl: copy-up on MAP_SHARED Miklos Szeredi
2016-11-25 21:20   ` [mm] 68ab21008a: BUG:unable_to_handle_kernel kernel test robot
2016-11-24 10:55 ` [PATCH 4/7] ovl: add infrastructure for intercepting file ops Miklos Szeredi
2016-11-24 11:52   ` Amir Goldstein
2016-11-24 12:03     ` Miklos Szeredi
2016-11-24 13:12       ` Amir Goldstein
2016-11-24 13:51         ` Miklos Szeredi
2016-11-24 14:08           ` Amir Goldstein
2016-11-25  5:22             ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 5/7] ovl: intercept read_iter Miklos Szeredi
2016-11-24 10:55 ` [PATCH 6/7] ovl: intercept mmap Miklos Szeredi
2016-11-24 13:25   ` Amir Goldstein
2016-11-24 18:03     ` Amir Goldstein
2016-11-24 19:06       ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 7/7] ovl: intercept fsync Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1479984944-1017-2-git-send-email-mszeredi@redhat.com \
    --to=mszeredi@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).