RFC i_version update for ext4

Cordenner jean noel linux-ext4 1 version Jan 23, 2007 In review

Get series with b4

b4 am [email protected]

Versions newest first

v1 RFC Latest Jan 23, 20073 patches 10 repliesIn review

Patches in v1 No applies recorded yet

#	Subject and files	Size	Replies
1/3	i_version update for ext4: VFS layer`fs/attr.c 2007-01-22 17:03:41.000000000 +0100` `fs/bad_inode.c 2007-01-22 17:04:58.000000000 +0100` `fs/binfmt_misc.c 2007-01-22 17:05:54.000000000 +0100` +3 more	+16 ~~-11~~	0 replies
2/3	i_version update for ext4: ext4 specific code`fs/ext4/ialloc.c 2007-01-23 13:48:20.000000000 +0100` `fs/ext4/inode.c 2007-01-23 13:45:02.000000000 +0100` `fs/ext4/ioctl.c 2007-01-23 13:49:58.000000000 +0100` +4 more	+13 -3	2 replies
3/3	i_version update for ext4: user interface`fs/stat.c 2007-01-23 16:21:17.000000000 +0100` `include/asm-i386/stat.h 2007-01-23 17:48:36.000000000 +0100` `include/asm-x86_64/stat.h 2007-01-23 17:57:03.000000000 +0100` +1 more	+8 -3	3 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC] [patch 0/3] i_version update for ext4

Hello,

I've updated what was previously the change attribute patch for ext4 initially posted by Alexandre Ratchov. The previous patch was introducing a change_attribute field, now it uses the i_version field of the inode.

The i_version field is a counter that is set on every inode creation and that is incremented every time the inode data is modified (similarly to the "ctime" time-stamp). The aim is to fulfill NFSv4 requirements for rfc3530.
For the moent, the counter is only a 32bit value but it is planned to be 64bit as required.

The patch is divided into 3 parts, the vfs layer, the ext4 specific code and an user part to check i_version changes via stat.

Any comments are welcome.

regards,
Jean noel

Read the cover letter in its thread