[PATCH 2/2] vfs: support for COW files in sys_open: filesystem changes

["Carl Spalletta" <cspalletta@gmail.com>]

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)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/