linux-ext4 - Re: [PATCH] filefrag: don't print extent header on bmap fallback

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090816035032.GD17958@mit.edu>
Date:	Sat, 15 Aug 2009 23:50:32 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] filefrag: don't print extent header on bmap fallback

On Wed, Aug 05, 2009 at 10:30:48PM -0500, Eric Sandeen wrote:
> The extent list header gets printed before we fall back to bmap:
> 
> # filefrag -v /mnt/test/bar
> Filesystem type is: 58465342
> File size of /mnt/test/bar is 12288 (3 blocks, blocksize 4096)
>  ext logical physical expected length flags <---- HERE
> Discontinuity: Block 2 is at 17 (was 16)
> /mnt/test/bar: 2 extents found
> 
> so delay printing it until we know fiemap is working.
> 
> (though ideally it'd be nice to have the same verbose output
> regardless of the interface we used, I think).

Thanks, applied.

					- Ted
--
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