From: Pavel Machek <pavel@ucw.cz>
To: carl <cspalletta@gmail.com>
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 1/1] vfs: support for COW files in sys_open
Date: Sat, 17 Jun 2006 05:16:58 +0000 [thread overview]
Message-ID: <20060617051657.GA7464@ucw.cz> (raw)
In-Reply-To: <20060609165321.66EEC118601@localhost.localdomain>
Hi!
> Giving the O_COW flag to open() will return a special error, if
> IS_COW(inode) and write permissions are expressed or implied. COW-aware
> applications may set this flag and deal with this error according to
> some user defined policy. This will not change the semantics of any
> existing application or affect any kernel user of open_namei(); nor does
> it affect future applications unless they use O_COW. Filesystem level
> code is unimplemented except for an ext2 example.
Can you give us overview how this is used? COW for ext2 seems nice...
Is the plan to allow cp -a --cow linux linux.new ?
Pavel
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-06-17 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 16:53 [PATCH 1/1] vfs: support for COW files in sys_open carl
2006-06-17 5:16 ` Pavel Machek [this message]
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=20060617051657.GA7464@ucw.cz \
--to=pavel@ucw.cz \
--cc=cspalletta@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.