linux-kernel - Re: What happened to data=guarded?

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: <200908112200.n7BM0FSK070363@neskaya.eckenfels.net>
Date:	Wed, 12 Aug 2009 00:00:15 +0200 (CEST)
From:	Bernd Eckenfels <bernd-09@...enfels.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: What happened to data=guarded?

In article <20090810164205.GC1505@....cz> you wrote:
>> What sort of files were you losing?  I don't know if we can improve
>> the implied flush hueristics, but we should at least try to see if we
>> do something about it.
> 
> IIRC... the flush heuristics invoke async flush, so you can still lose
> data if you are unlucky, no?

BTW: one good heuristic would be to flush() files on close async but if the
file is renamed fush it sync before the rename.  The typical close temp file
and rename it would work without a fdatasync().

Gruss
Bernd
--
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/