linux-kernel - RE: open(O_DIRECT) on a tmpfs?

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: <Pine.LNX.4.64.0701041911470.27405@blonde.wat.veritas.com>
Date:	Thu, 4 Jan 2007 19:14:04 +0000 (GMT)
From:	Hugh Dickins <hugh@...itas.com>
To:	Hua Zhong <hzhong@...il.com>
cc:	Christoph Hellwig <hch@...radead.com>,
	'Bill Davidsen' <davidsen@....com>,
	'Linux-kernel' <linux-kernel@...r.kernel.org>
Subject: RE: open(O_DIRECT) on a tmpfs?

On Thu, 4 Jan 2007, Hua Zhong wrote:
> 
> So I'd argue that it makes more sense to support O_DIRECT
> on tmpfs as the memory IS the backing store.

A few more voices in favour and I'll be persuaded.  Perhaps I'm
out of date: when O_DIRECT came in, just a few filesystems supported
it, and it was perfectly normal for open O_DIRECT to be failed; but
I wouldn't want tmpfs to stand out now as a lone obstacle.

Christoph, what's your take on this?

Hugh
-
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/