| 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
| ||
|
Message-ID: <4DA2E102.5080801@draigBrady.com> Date: Mon, 11 Apr 2011 12:07:46 +0100 From: Pádraig Brady <P@...igBrady.com> To: coreutils@....org, linux-ext4@...r.kernel.org Subject: Re: ready for release of coreutils-8.11? On 09/04/11 00:37, Pádraig Brady wrote: > One thing I'm worried about is fiemap with compressed file systems. > I'm unsure that the extent length refers to the length of > the unencoded data. That's what I would expect so that > user space is abstracted from encoding details and so > we know how much to read to fully process an extent. > > I've not got a new BTRFS kernel readily available at present > to do a quick test. I'll try to text tomorrow night. I've tried various BTRFS combinations here with 2.6.38.2-9.fc15.i686. I'm using `mount -o compress -o compress-force`, but any files copied into the file system, don't have FIEMAP_EXTENT_ENCODED flags, and du doesn't indicate that less space is used in the file system. So I'm assuming that the compression is below the file system, and doesn't increase the space available. I.E. it's just there to more efficiently write blocks to disk. As for the FIEMAP_EXTENT_ENCODED flag, are there any uses currently? Note coreutils currently assumes that the length of an extent, is that required to read it fully, even in the presence of implicit conversion. cheers, Pádraig. -- 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
Powered by blists - more mailing lists