linux-kernel - On the workings of mmap

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]

Date:	Thu, 17 Dec 2009 16:06:28 -0200
From:	Rafael Almeida <almeidaraf@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: On the workings of mmap

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.

[]'s
Rafael
--
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/