linux-ext4 - Re: [PATCH RFC] Insure direct IO writes do not use the page cache

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 31 Jul 2009 11:03:07 -0700
From:	Michael Rubin <mrubin@...gle.com>
To:	Mingming <cmm@...ibm.com>
Cc:	Theodore Tso <tytso@....edu>, Jan Kara <jack@...e.cz>,
	Curt Wohlgemuth <curtw@...gle.com>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH RFC] Insure direct IO writes do not use the page cache

On Fri, Jul 31, 2009 at 10:58 AM, Mingming<cmm@...ibm.com> wrote:
> Eric and I looked at xfs code together the other day, xfs code did not
> ensure DIO sync metadata (conversion) before return back to userspace.
> It does ensure the workqueue kickoff the conversion and journal commit,
> but it seems not waiting for it to complete. This seems confirmed by xfs
> expert on IRC, who expressed DIO means only bypass page cache, but not
> necessarily means sync on data and metadata unless file is opened with
> SYNC mode.

This will our expectations for DIO on ext4 also.

mrubin
--
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