Date: Fri, 20 Nov 2009 22:11:08 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bernd Petrovitsch <bernd@firmix.at>, linux-kernel@vger.kernel.org,
       Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: O_NOATIME and files in /proc
Message-ID: <20091120221108.1fb1dfcf@lxorguk.ukuu.org.uk>
In-Reply-To: <20091120133651.9df2da80.akpm@linux-foundation.org>
References: <1258477590.16246.35.camel@tara.firmix.at>
	<20091120133651.9df2da80.akpm@linux-foundation.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 886
Lines: 23

On Fri, 20 Nov 2009 13:36:51 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Tue, 17 Nov 2009 18:06:29 +0100
> Bernd Petrovitsch <bernd@firmix.at> wrote:
> 
> > Hi all!
> > 
> > Is there a specific reason that open can not open files (at
> > least /proc/noatime and /proc/cpuinfo) under /proc with NO_ATIME as the
> > following program shows:

Andreww: http://lkml.org/lkml/2004/6/14/184 seems to explain the origin
of this. To follow it further you'd need to discuss it with Ulrich I
imagine and see why glibc expected that behaviour and in turn where it
came from and what security or similar concerns were anticipated.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/