[2.6.27-2.3] /proc/sys/vm/mmap_min_addr does not work (regression)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King |
Bug Description
=======
FAIL: Verify lower 64k of memory is not allocatable
-------
Traceback (most recent call last):
File "./kernel-
self.
File "./kernel-
self.
AssertionError: Got exit code 1, expected 0
Command: './low-mmap'
Output:
Testing lower 64k in 4096 byte chunks:
Unexpectedly allocated 4096 bytes at 0x00000000
Unexpectedly allocated 4096 bytes at 0x00001000
Unexpectedly allocated 4096 bytes at 0x00002000
Unexpectedly allocated 4096 bytes at 0x00003000
Unexpectedly allocated 4096 bytes at 0x00004000
Unexpectedly allocated 4096 bytes at 0x00005000
Unexpectedly allocated 4096 bytes at 0x00006000
Unexpectedly allocated 4096 bytes at 0x00007000
Unexpectedly allocated 4096 bytes at 0x00008000
Unexpectedly allocated 4096 bytes at 0x00009000
Unexpectedly allocated 4096 bytes at 0x0000a000
Unexpectedly allocated 4096 bytes at 0x0000b000
Unexpectedly allocated 4096 bytes at 0x0000c000
Unexpectedly allocated 4096 bytes at 0x0000d000
Unexpectedly allocated 4096 bytes at 0x0000e000
Unexpectedly allocated 4096 bytes at 0x0000f000
FAIL
Testing 4096 byte chunk above 64k: pass
$ cat /proc/sys/
65536
The mmap_min_addr feature does not appear to be working, yet AA still has the mmap_min_addr patch:
http://
Changed in linux: | |
milestone: | none → ubuntu-8.10-beta |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → High |
status: | New → Triaged |
Changed in linux: | |
assignee: | ubuntu-kernel-team → colin-king |
status: | Triaged → In Progress |
Hi Kees,
Can you attach the python script that does this test - I tried to reproduce this with the attached program and could not reproduce it with 2.6.27-2.3 or higher so I suspect my test program may be doing mmap's differently.
Thanks, Colin.