linux-kernel - Re: [rfc] Ignore Fsync Calls in Laptop

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: <148710.1306760150@turing-police.cc.vt.edu>
Date:	Mon, 30 May 2011 08:55:50 -0400
From:	Valdis.Kletnieks@...edu
To:	Oliver Neukum <oneukum@...e.de>
Cc:	david@...g.hm, "D. Jansen" <d.g.jansen@...glemail.com>,
	Theodore Tso <tytso@....edu>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Dave Chinner <david@...morbit.com>,
	njs@...ox.com, bart@...wel.tk
Subject: Re: [rfc] Ignore Fsync Calls in Laptop_Mode

On Mon, 30 May 2011 09:13:27 +0200, Oliver Neukum said:
> Am Montag, 30. Mai 2011, 03:53:18 schrieb david@...g.hm:

> > if what you are wanting is the ability to say 'these things must be 
> > written before these other things to keep them from being corrupted, but I 
> > don't care when they get written (or if they get lost in a crash)' then 
> > what you want isn't fsync, it's a barrier.
> 
> Yes, but where is the problem?

The problem is that *from userspace*, the closest approximation to a barrier
is fsync().

Content of type "application/pgp-signature" skipped