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
| ||
|
Date: Mon, 05 Mar 2007 16:00:06 -0600 From: Eric Sandeen <sandeen@...hat.com> To: Jörn Engel <joern@...ybastard.org> CC: Arnd Bergmann <arnd@...db.de>, Ulrich Drepper <drepper@...hat.com>, Anton Altaparmakov <aia21@....ac.uk>, Christoph Hellwig <hch@...radead.org>, Dave Kleikamp <shaggy@...ux.vnet.ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, "Amit K. Arora" <aarora@...ux.vnet.ibm.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, suparna@...ibm.com, cmm@...ibm.com, alex@...sterfs.com, suzuki@...ibm.com Subject: Re: [RFC] Heads up on sys_fallocate() Jörn Engel wrote: > Does the allocation have to be persistent beyond lifetime of the file > descriptor? It would be fairly simple to support the write guarantee > while the file is open (or rather the inode remains cached) and drop it > afterwards. "The posix_fallocate() function shall ensure that any required storage for regular file data starting at offset and continuing for len bytes is allocated on the file system storage media." I interpret "on the storage media" to mean that it is persistent. -Eric - 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