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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 18 Apr 2011 10:40:40 +1000
From:	Dave Chinner <>
To:	Theodore Tso <tytso@....EDU>
Cc:	Andreas Dilger <>,
	Pádraig Brady <>,
	Eric Sandeen <>,
	"" <>,
	"" <>,
	Markus Trippelsdorf <>,
	xfs-oss <>
Subject: Re: Files full of zeros with coreutils-8.11 and xfs (FIEMAP

On Sat, Apr 16, 2011 at 08:21:28AM -0400, Theodore Tso wrote:
> On Apr 16, 2011, at 1:11 AM, Andreas Dilger wrote:
> > In that case, it means cp should just always use FIEMAP_FLAG_SYNC, which is fine. 
> Except that if someone is copying a large delay allocated file, it will cause 
> the file to immediately snapped to disk, which might not be the greatest
> thing in the world. 

Obvious workaround - if the initial fiemap call shows unwritten
extents, redo it with the sync flag set. Though that assumeѕ that
you can trust things like delalloc extents to only cover the range
that valid data exists in. Which, of course, you can't assume,
either. :/

> Christoph is write, SEEK_HOLE and SEEK_DATA are
> a much better API for what cp woulld lke to do.  Unfortunately it hasn't
> been implemented yet in the VFS...

Agreed, SEEK_HOLE/SEEK_DATA is the right way to solve this problem.


Dave Chinner
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists