1 |
On 3 Apr 2009 at 2:04, Alex Efros wrote: |
2 |
|
3 |
> I think best way to find out what happens - add debug prints into PaX code |
4 |
> which executes while starting process N1. |
5 |
|
6 |
ok, can you add a printk into mm/mmap.c:mmap_region and print out all the |
7 |
arguments? that will show us at least what the kernel intended to mmap |
8 |
during execve. something like: |
9 |
|
10 |
printk("f:%p a:%0lx l:%0lx f:%0lx v:%0lx p:%0lx\n", file, addr, len, flags, vm_flags, pgoff); |
11 |
|
12 |
also to simplify matters, can you just run with the PaX test patch alone? |