linux-kernel - mmap: is default non-populating behavior stable?

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-next>] [day] [month] [year] [list]

Message-ID: <490F73CD.4010705@gmail.com>
Date:	Mon, 03 Nov 2008 23:57:33 +0200
From:	"Eugene V. Lyubimkin" <jackyf.devel@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: mmap: is default non-populating behavior stable?

Hello kernel hackers!

The current implementation of mmap() in kernel is very convenient.
It allows to mmap(fd) very big amount of memory having small file as back-end.
So one can mmap() 100 MiB on empty file, use first 10 KiB of memory, munmap() and have
only 10 KiB of file at the end. And while working with memory, file will automatically be
grown by read/write memory requests.

Question is: can user-space application rely on this behavior (I failed to find any
documentation about this)?

TIA and please CC me in replies.

-- 
Eugene V. Lyubimkin aka JackYF

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)