Re: FIEMAP patches

[Mark Fasheh <mfasheh@suse.com>]

On Mon, Aug 25, 2008 at 02:22:50PM -0600, Andreas Dilger wrote:
> I read through the entire previous FIEMAP thread (phew!) and it boils
> down mostly to:
> 
> s/FIEMAP_FLAG_NO_DIRECT/FIEMAP_FLAG_NO_BYPASS/
> 
> > * FIEMAP_EXTENT_UNWRITTEN                                                    
> > Unwritten extent - the extent is allocated but it's data has not been        
> > initialized.  This indicates the extent's data will be all zero.             
>                                                                                
> This should say "will be all zero if read through the filesystem              
> but the contents are undefined if read directly from the device."
> 
> There was also an update to the ext4 patch from Kalpak for handling
> EA-in-inode at the same time as an external inode.

Hmm, I didn't find this in my mailbox... The Ext4 patch I had doesn't apply
any more either :( I think one of you all is going to have to send an
update.


> Eric, Mark,
> could one of you please just submit the patches to Andrew for inclusion.
> I think there was plenty of debate already, with very little significant
> benefit except suggesting different names for some of the flags.

Ok, sorry again for the delay. I am at a conference this week, then on
vacation, then back to another conference, so I am having a rather busy
month. None the less, I managed to bring the fiemap patches up to
2.6.27-rc6, with the changes discussed.

They are in git:

git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git fiemap

Individual patches will be mailed in response to this message.


Andrew, are these patches ok for a spin in -mm? I agree with Andreas that
this has been discussed to death, with very little benefit being extracted
from the latest round.
	--Mark

--
Mark Fasheh