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: <alpine.DEB.2.02.1105271050160.30828@asgard.lang.hm>
Date:	Fri, 27 May 2011 10:51:08 -0700 (PDT)
From:	david@...g.hm
To:	Theodore Tso <tytso@....EDU>
cc:	"D. Jansen" <d.g.jansen@...glemail.com>,
	Oliver Neukum <oneukum@...e.de>, 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 Fri, 27 May 2011, Theodore Tso wrote:

> If you are willing to rewrite the *entire* database to a completely new file each
> time you want to write out some data, and only delete the old database
> once the new database has been written out, then you're fine.   If the file is too
> big you can delay the time period between a complete writeout of the
> database.  But then if you drop your laptop and the battery slips out, you'll
> lose more data.  Life is full of tradeoffs.

actually, even in this case don't you need a barrier or fsync to make sure 
the new file is completely written before the old file goes away?

David Lang
--
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/