linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jan Kara <jack@suse.com>, Christoph Hellwig <hch@lst.de>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 0/5] overlayfs: support freeze/thaw
Date: Tue, 31 Jan 2017 10:34:54 +0200	[thread overview]
Message-ID: <1485851699-25313-1-git-send-email-amir73il@gmail.com> (raw)

Miklos,

Patches 1-3 address your review comments and some
issues I found with fallocate() and copy_file_range()
helpers.
They are supposed to replace the patch already in overlayfs-next
97e147358bea ("vfs: wrap write f_ops with file_{start,end}_write()")

Let me know if you want me to rebase them on top of the already
committed change.

Patches 4-5 implement overlayfs freeze and are more of an RFC
at this point, but they are tested.

v3:
- Verify regular file before calling file_start_write()

v2:
- file_start_write() gets freeze protection on both upper and overlay
- convert file ops wraped with sb_start_write() to file_start_write()

v1:
- freeze upper on freeze of overlay

Amir Goldstein (5):
  vfs: deny fallocate() on directory
  vfs: deny copy_file_range() for non regular files
  vfs: wrap write f_ops with file_{start,end}_write()
  vfs: freeze protect overlay inode on file_start_write()
  ovl: support freeze/thaw super

 fs/open.c            | 14 ++++++--------
 fs/overlayfs/super.c | 12 ++++++++++++
 fs/read_write.c      |  9 +++++++--
 include/linux/fs.h   | 43 +++++++++++++++++++++++++++++--------------
 4 files changed, 54 insertions(+), 24 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-01-31  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  8:34 Amir Goldstein [this message]
2017-01-31  8:34 ` [PATCH v3 1/5] vfs: deny fallocate() on directory Amir Goldstein
2017-01-31 10:56   ` Christoph Hellwig
2017-01-31  8:34 ` [PATCH v3 2/5] vfs: deny copy_file_range() for non regular files Amir Goldstein
2017-01-31 10:56   ` Christoph Hellwig
2017-01-31  8:34 ` [PATCH v3 3/5] vfs: wrap write f_ops with file_{start,end}_write() Amir Goldstein
2017-01-31 10:56   ` Christoph Hellwig
2017-01-31  8:34 ` [PATCH v3 4/5] vfs: freeze protect overlay inode on file_start_write() Amir Goldstein
2017-01-31  8:34 ` [PATCH v3 5/5] ovl: support freeze/thaw super Amir Goldstein

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=1485851699-25313-1-git-send-email-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=hch@lst.de \
    --cc=jack@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@zeniv.linux.org.uk \
    /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).