From: "Carl Spalletta" <cspalletta@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk
Subject: [PATCH 2/2] vfs: support for COW files in sys_open: filesystem changes
Date: Thu, 8 Jun 2006 16:51:38 -0400 [thread overview]
Message-ID: <69a7202e0606081351i1ec473f7jd608397282c983da@mail.gmail.com> (raw)
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.
Signed-off-by: Carl Spalletta <cspalletta@gmail.com>
---
include/linux/ext2_fs.h | 1 +
fs/ext2/inode.c | 2 ++
2 files changed, 3 insertions(+)
--- a/include/linux/ext2_fs.h 2006-06-07 11:19:11.000000000 -0400
+++ b/include/linux/ext2_fs.h 2006-06-06 13:26:38.000000000 -0400
@@ -192,6 +192,7 @@ struct ext2_group_desc
#define EXT2_NOTAIL_FL 0x00008000 /* file tail should
not be merged */
#define EXT2_DIRSYNC_FL 0x00010000 /* dirsync
behaviour (directories only) */
#define EXT2_TOPDIR_FL 0x00020000 /* Top of directory
hierarchies*/
+#define EXT2_COW_FL 0x00040000 /* Hint to
COW-aware applications */
#define EXT2_RESERVED_FL 0x80000000 /* reserved for ext2 lib */
#define EXT2_FL_USER_VISIBLE 0x0003DFFF /* User visible flags */
--- a/fs/ext2/inode.c 2006-06-07 11:19:12.000000000 -0400
+++ b/fs/ext2/inode.c 2006-06-06 13:32:28.000000000 -0400
@@ -1065,6 +1065,8 @@ void ext2_set_inode_flags(struct inode *
inode->i_flags |= S_NOATIME;
if (flags & EXT2_DIRSYNC_FL)
inode->i_flags |= S_DIRSYNC;
+ if (flags & EXT2_COW_FL)
+ inode->i_flags |= S_COW;
}
void ext2_read_inode (struct inode * inode)
reply other threads:[~2006-06-08 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69a7202e0606081351i1ec473f7jd608397282c983da@mail.gmail.com \
--to=cspalletta@gmail.com \
--cc=cspalletta@adelphia.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®