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: Tue, 26 Feb 2008 07:13:29 -0500 From: Ric Wheeler <ric@....com> To: Jeff Garzik <jeff@...zik.org> CC: Jamie Lokier <jamie@...reable.org>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, Chris Wedgwood <cw@...f.org> Subject: Re: Proposal for "proper" durable fsync() and fdatasync() Jeff Garzik wrote: > Jamie Lokier wrote: >> By durable, I mean that fsync() should actually commit writes to >> physical stable storage, > > Yes, it should. > > >> I was surprised that fsync() doesn't do this already. There was a lot >> of effort put into block I/O write barriers during 2.5, so that >> journalling filesystems can force correct write ordering, using disk >> flush cache commands. >> >> After all that effort, I was very surprised to notice that Linux 2.6.x >> doesn't use that capability to ensure fsync() flushes the disk cache >> onto stable storage. > > It's surprising you are surprised, given that this [lame] fsync behavior > has remaining consistently lame throughout Linux's history. Maybe I am confused, but isn't this is what fsync() does today whenever barriers are enabled (the fsync() invalidates the drive's write cache). ric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists