linux-kernel - Non continuous VM address space

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: <2fe399760704261333g4dbf79a1p92be761d3680c9d7@mail.gmail.com>
Date:	Thu, 26 Apr 2007 13:33:41 -0700
From:	"Phy Prabab" <phyprabab@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Non continuous VM address space

Hello,

I have a question, I have a little application and sbrks and then
mmaps to get memory from the system.  Originally, this program worked
fine because I had assumed that my applications address space would be
continuous, each subsequent memory request would "mapped" next to each
other, after all this is the address space for this process.  However,
what I am finding is that the space is discontiguous, I am getting
back addresses not next to each other.  Sometimes the next memory
allocation is several megs above where the previous mapping came from.
 Is this possible?  Or am I not accounting for something?  Yes, I have
intentionally defined malloc, calloc, etc. so they can not be used
under the hood within my code.

BTW, seeing this on 2.6.9 and 2.4.(?) - these are both RH supplied kernels

TIA!
Phy
-
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/