From: David Howells <dhowells@redhat.com>
To: Colin Walters <walters@verbum.org>
Cc: dhowells@redhat.com, miklos@szeredi.hu, viro@ZenIV.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file
Date: Wed, 10 Jun 2015 17:12:51 +0100 [thread overview]
Message-ID: <17649.1433952771@warthog.procyon.org.uk> (raw)
In-Reply-To: <1433950405.375893.291973049.101362CB@webmail.messagingengine.com>
Colin Walters <walters@verbum.org> wrote:
> On Thu, May 28, 2015, at 02:46 PM, David Howells wrote:
> > Print a warning when overlayfs copies up a file if the process that
> > triggered the copy up has a R/O fd open to the lower file being copied up.
>
> Why not an option to make it an error? If one's goal is to use overlayfs
> without apps potentially corrupting data, better to fail fast.
That could be added. Note that doing this isn't *necessarily* wrong though.
David
next prev parent reply other threads:[~2015-06-10 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 18:46 [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file David Howells
2015-06-10 13:23 ` David Howells
2015-06-10 15:33 ` Colin Walters
2015-06-10 16:12 ` David Howells [this message]
2015-06-22 15:10 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2015-07-07 14:04 David Howells
2016-03-07 10:06 ` 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=17649.1433952771@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
--cc=walters@verbum.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).