linux-kernel - Re: writing file to disk: not as easy as it looks

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.64.0812031840420.25439@artax.karlin.mff.cuni.cz>
Date:	Wed, 3 Dec 2008 18:43:18 +0100 (CET)
From:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To:	Theodore Tso <tytso@....edu>
cc:	Pavel Machek <pavel@...e.cz>, Chris Friesen <cfriesen@...tel.com>,
	kernel list <linux-kernel@...r.kernel.org>, aviro@...hat.com
Subject: Re: writing file to disk: not as easy as it looks

> On Wed, Dec 03, 2008 at 09:46:40AM +0100, Pavel Machek wrote:
> > Yes. fsync() seeems surprisingly high on Rusty's list of broken
> > interfaces classification ('impossible to use correctly').

BTW where is that list.

> To be fair, fsync() was primarily intended for making sure that the
> data had been written to disk, and not necessarily as a way of making
> sure that write errors would be properly reflected back to the
> application.  As you've pointed out, it's not really adequate for that
> purpose.
> 
> 						- Ted

Well, what else do you want to use for databases? (where crashing the 
whole computer makes less damage than pretending that transaction was 
committed while it wasn't).

Mikulas
--
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/