Date: Thu, 17 Dec 2009 18:49:35 +0000 (GMT)
From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Rafael Almeida <almeidaraf@gmail.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: On the workings of mmap
In-Reply-To: <6de6b1650912171006j2ac942ay1f31286a05248433@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0912171842510.30830@sister.anvils>
References: <6de6b1650912171006j2ac942ay1f31286a05248433@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 25

On Thu, 17 Dec 2009, Rafael Almeida wrote:

> Hello. I have been studying the mmap function and it seems like when I
> map an sparse file, that the parts of the file that have nothing are
> defined as 0 when I access them through the address space returned by
> mmap. Is that luck or is it defined to be this way? My only source of
> information was debian's manpage on mmap that didn't seem to talk
> about sparse files at all.

That's not luck, it is required to be that way.

Though I've not located such a definition with respect to mmap(),
it would be perverse if mmap() showed you different data there from
what read() shows you, and the Single Unix Specification (Version 3)
says of read():

"If any portion of a regular file prior to the end-of-file has not
 been written, read() shall return bytes with value 0."

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