linux-ext4 - Re: [RFC][PATCH] fiemap support for ext3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <20080422023315.GR2775@webber.adilger.int>
Date:	Mon, 21 Apr 2008 20:33:15 -0600
From:	Andreas Dilger <adilger@....com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Josef Bacik <jbacik@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: [RFC][PATCH] fiemap support for ext3

On Apr 21, 2008  17:16 -0500, Eric Sandeen wrote:
> Andreas Dilger wrote:
> > Josef, thanks for doing this work.  Having more than a single filesystem
> > implement FIEMAP (especially a block-mapped one) is very useful.  
> 
> I have an xfs patch too if anyone wants it ;)

Please, do send it on to Dave Chinner.  He was one of the main contributors
to the FIEMAP specification.  He could also give another opinion on whether
the NUM_EXTENTS should return an "extent" for a hole or not.

> So hopefully we can roll out at least 3 fs's when it goes upstream.
> 
> > Did you
> > look at all at making a "generic_fiemap()" function?  It seems very little
> > of ext3_fiemap() is ext3 specific, only the call to ext3_force_commit()
> > (which could just be a sync on the inode), ext3_block_map() (generic for
> > all block-based filesystems), and truncate_mutex (would i_sem be enough?).
> 
> Yep, I agree, it'd be good if ! ->fiemap then go the generic route.
> 
> Although my only question/worry is do all filesystems behave sanely in
> the face of large b_size for getblocks?  All that can handle direct IO
> do anyway.
> 
> >> +int ext3_fiemap(struct inode *inode, unsigned long arg)
> >> +{
> >> +	/*
> >> +	 * if fm_start is in the middle of the current block, get the next
> >> +	 * block so we don't end up returning a start thats before the given
> >> +	 * fm_start
> >> +	 */
> >> +	start_blk = (fiemap_s->fm_start + (1 << inode->i_blkbits) - 1) >>
> >> +		inode->i_blkbits;
> > 
> > Hmm, I'd think that if someone is requesting the mapping for bytes [50-5000]
> > they wouldn't be very happy with the mapping returned being [4096-8191],
> > because it is missing part of the requested range.  Instead, the fm_start
> > should be rounded down to the start of the first block and up to the end
> > of the last block to return [0-8191] (fm_start = 0, fm_length = 8192).
> 
> In fact that should be part of the interface definition, right.  Should
> the returned mapping start at the beginning of the block that contains
> the requsted offset, or at the requested offset itself?  I'd vote for
> the former.
> 
> At some point I should probably write some QA for this thing to test
> various file layouts and make sure we get the "right" answers on all
> filesystems...
> 
> -Eric

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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