the thing is that they are not. the kernel chooses to REPLACE my mapping.
consider the user-space code:
mmap(0xaaaa0000, 0x3000, MAP_FIXED, ...);
mmap(0xaaaa1000, 0x4000, MAP_FIXED, ...);
here, the second call to mmap will shorten the first mapping to 0x1000 bytes
and create one big vma with size 0x5000 bytes.
is there a way to tell it that the second mmap MUST fail?
-