Date: Thu, 28 Aug 2003 12:08:21 +0200
From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Lockless file reading
Message-ID: <20030828100821.GB5040@merlin.emma.line.org>
Mail-Followup-To: linux-kernel@vger.kernel.org
References: <1061987837.1455.107.camel@hurina> <200308271442.48672.martin.konold@erfrakon.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200308271442.48672.martin.konold@erfrakon.de>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 827
Lines: 25

On Wed, 27 Aug 2003, Martin Konold wrote:

> Am Wednesday 27 August 2003 02:37 pm schrieb Timo Sirainen:
> 
> Hi,
> 
> > The question is what can happen if I read() a file that's being
> > simultaneously updated by a write() in another process?
> 
> The behaviour is undefined.
>  
> > 123 over XXX, is it possible that read() returns 1X3 in some conditions?
> 
> Yes. The actual order stuff is written to the disk is not guaranteed.

What has the disk block write order got to do with it? It's not as
though write() would be cached but read() see the raw disk.

-- 
Matthias Andree
-
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/