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: <459D56FE.5080600@rtr.ca>
Date:	Thu, 04 Jan 2007 14:35:26 -0500
From:	Mark Lord <lkml@....ca>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	Hua Zhong <hzhong@...il.com>,
	Christoph Hellwig <hch@...radead.com>,
	'Bill Davidsen' <davidsen@....com>,
	'Linux-kernel' <linux-kernel@...r.kernel.org>
Subject: Re: open(O_DIRECT) on a tmpfs?

Hugh Dickins wrote:
> 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. 

I see no reason to restrict it as is currently done.

Policy belongs in userspace, not in the kernel,
so long as the code impact is miniscule.

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