| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 4/9] xfs: move v1 inode conversion to xfs_inode_from_disk |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 9 Feb 2016 06:44:18 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160208093150.GD28146@xxxxxxxxxxxxx> |
| References: | <1454905461-2773-1-git-send-email-david@xxxxxxxxxxxxx> <1454905461-2773-5-git-send-email-david@xxxxxxxxxxxxx> <20160208093150.GD28146@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Feb 08, 2016 at 01:31:50AM -0800, Christoph Hellwig wrote: > Looks fine, > > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > > Shouldn't we be able to kill off di_version as well? version 3 inodes > only happen on crc enabled file systems, and version 2 only on > version 4 file systems. In theory, yes, though there is a lot of code that checks the di_version field and the superblock version checks are more heavyweight. I think it's also a cleaner design to base general inode formatting decisions on the inode version number and it's internal flags, because then we don't have to rely on external code to determine exactly what to do. e.g. in userspace there is no guarantee we have a superblock context we can access, even if we have a struct xfs_inode or a struct xfs_icdinode... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: [PATCH 1/9] xfs: introduce inode log format object, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH 6/9] xfs: use vfs inode nlink field everywhere, Dave Chinner |
| Previous by Thread: | Re: [PATCH 4/9] xfs: move v1 inode conversion to xfs_inode_from_disk, Christoph Hellwig |
| Next by Thread: | [PATCH 1/9] xfs: introduce inode log format object, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |