Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Kalpak Shah <kalpak@clusterfs.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
	Andreas Dilger <adilger@clusterfs.com>,
	Jean noel Cordenner <jean-noel.cordenner@bull.net>
Subject: Re: [PATCH 0/6] inode version updated patches
Date: Thu, 14 Jun 2007 13:48:59 -0700	[thread overview]
Message-ID: <1181854139.3883.7.camel@dyn9047017103.beaverton.ibm.com> (raw)
In-Reply-To: <1181836571.7779.42.camel@garfield>

On Thu, 2007-06-14 at 21:26 +0530, Kalpak Shah wrote:
> Hi,
> 
> I have updated the inode version patches and below are the details:
> 
> 64-bit-i_version.patch which only replaces the 32-bit i_version field in
> the generic inode with a 64-bit i_version field. The VFS-level updates
> of the inode version are still in the i_version_update_vfs.patch and
> this patch has been moved to the bottom of the patch series.
> 
> ext4_i_version_hi_2.patch was still using ei->i_fs_version instead of
> inode->i_version. I have corrected this patch.
> 
> Also there were whitespace problems in i_version_hi.patch.
> 
> I am also attaching a ext4_no_version.patch which adds a "noversion"
> mount option to disable inode version updates.
> 
> I am not sure why i_version needs to be updated in VFS since it is being
> updated in ext4_mark_iloc_dirty().
> 

Yes I think we can remove the inode version update in VFS patch. So I am
going to drop the patch 5/6.  Jean Noel, if you disagree, please let me
know.

> Well, these are lots of small patches and I am sending them separately
> so that they can be applied and commented upon easily.
> 

Thanks, I will update the patch queue with your patch series.

Mingming
> Thanks,
> Kalpak.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-06-14 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 15:56 [PATCH 0/6] inode version updated patches Kalpak Shah
2007-06-14 20:48 ` Mingming Cao [this message]
2007-06-15 14:28   ` Jean noel Cordenner

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=1181854139.3883.7.camel@dyn9047017103.beaverton.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=jean-noel.cordenner@bull.net \
    --cc=kalpak@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    /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