linux-ext4 - async commit & write barrier code

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-next>] [day] [month] [year] [list]

Message-ID: <48D7D3DF.70505@redhat.com>
Date:	Mon, 22 Sep 2008 13:20:31 -0400
From:	Ric Wheeler <rwheeler@...hat.com>
To:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: async commit & write barrier code

After today's call, I was poking around a bit to try and understand 
better how the async commit code plays with the write barrier.

journal_submit_commit_record seems to disable the barriers when async IO 
is enabled if I read the code correctly. If this is true, how can we 
provide any promises of on disk data integrity after an fsync()?

Regards,

Ric

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html