On Sun, 01 Jul 2007 03:37:45 -0400
Mingming Cao <[EMAIL PROTECTED]> wrote:

> This patch is on top of i_version_update_vfs.
> The i_version field of the inode is set on inode creation and incremented when
> the inode is being modified.
> 

Again, I don't think I've ever seen this patch before.  It is at least a
month old.

> 
> Index: linux-2.6.22-rc4/fs/ext4/ialloc.c
> ===================================================================
> --- linux-2.6.22-rc4.orig/fs/ext4/ialloc.c    2007-06-13 17:16:28.000000000 
> -0700
> +++ linux-2.6.22-rc4/fs/ext4/ialloc.c 2007-06-13 17:24:45.000000000 -0700
> @@ -565,6 +565,7 @@ got:
>       inode->i_blocks = 0;
>       inode->i_mtime = inode->i_atime = inode->i_ctime = ei->i_crtime =
>                                                      ext4_current_time(inode);
> +     inode->i_version = 1;
>  
>       memset(ei->i_data, 0, sizeof(ei->i_data));
>       ei->i_dir_start_lookup = 0;
> Index: linux-2.6.22-rc4/fs/ext4/inode.c
> ===================================================================
> --- linux-2.6.22-rc4.orig/fs/ext4/inode.c     2007-06-13 17:21:29.000000000 
> -0700
> +++ linux-2.6.22-rc4/fs/ext4/inode.c  2007-06-13 17:24:45.000000000 -0700
> @@ -3082,6 +3082,7 @@ int ext4_mark_iloc_dirty(handle_t *handl
>  {
>       int err = 0;
>  
> +     inode->i_version++;
>       /* the do_update_inode consumes one bh->b_count */
>       get_bh(iloc->bh);
>  
> Index: linux-2.6.22-rc4/fs/ext4/super.c
> ===================================================================
> --- linux-2.6.22-rc4.orig/fs/ext4/super.c     2007-06-13 17:19:11.000000000 
> -0700
> +++ linux-2.6.22-rc4/fs/ext4/super.c  2007-06-13 17:24:45.000000000 -0700
> @@ -2846,8 +2846,8 @@ out:
>               i_size_write(inode, off+len-towrite);
>               EXT4_I(inode)->i_disksize = inode->i_size;
>       }
> -     inode->i_version++;
>       inode->i_mtime = inode->i_ctime = CURRENT_TIME;
> +     inode->i_version = 1;
>       ext4_mark_inode_dirty(handle, inode);
>       mutex_unlock(&inode->i_mutex);
>       return len - towrite;

ext4 already has code to update i_version on directories.  Here we appear
to be udpating it on regular files?

But for what reason?  The changelog doesn't say?

AFAICT the code forgets to update i_version during file overwrites (unless
the overwrite was over a hole).  But without a decent description of this
change I cannot tell whether this was a bug.

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to