linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Olszak <j.olszak@samsung.com>
To: David Howells <dhowells@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: Optional switching off cow in overlayfs
Date: Tue, 23 Jun 2015 18:07:59 +0200	[thread overview]
Message-ID: <5589845F.5080206@samsung.com> (raw)
In-Reply-To: <32715.1435065828@warthog.procyon.org.uk>


On 06/23/2015 03:23 PM, David Howells wrote:
> Jan Olszak <j.olszak@samsung.com> wrote:
>
>> Why not just say: "rename causes copy" and leave everything as it is now.
> That's another option - but your whole proposal was that we specifically don't
> copy up these files IIRC.
>

Yes, so let's modify the proposal:

Overlayfs checks xattr "trusted.overlay.cow" to switch COW off whenever 
it's possible.

1. This would be an optimization/convenience option, not a security option
2. By default overlayfs uses COW like it does now
3. trusted.overlay.cow=="n" means:
- Unlink, open, setattr etc. use the original inode from lowerdir
- Unmodifying operations also use inode from lowerdir
- Other operations (rename) may copy the file if it's required by the 
implementation of overlayfs

Thanks,
Jan

  parent reply	other threads:[~2015-06-23 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 13:25 Optional switching off cow in overlayfs Jan Olszak
2015-06-18 13:39 ` David Howells
2015-06-18 14:43   ` Jan Olszak
2015-06-22 11:32     ` Miklos Szeredi
2015-06-22 13:45       ` Jan Olszak
2015-06-22 13:53         ` Miklos Szeredi
2015-06-22 14:26           ` Jan Olszak
2015-06-22 14:37             ` Miklos Szeredi
2015-06-22 15:32               ` Jan Olszak
2015-06-23  9:27                 ` David Howells
2015-06-23 10:36                   ` Jan Olszak
2015-06-23 13:23                     ` David Howells
2015-06-23 16:05                       ` Jan Olszak
2015-06-23 16:07                       ` Jan Olszak [this message]
2015-06-24 16:03                         ` Jan Olszak

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=5589845F.5080206@samsung.com \
    --to=j.olszak@samsung.com \
    --cc=dhowells@redhat.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).