grsecurity forums

It appears that PAX with PAGEEXEC enabled on sparc64 seems to cause issues for 64bit dynamically linked executables:

PAX: From 127.0.0.1: execution attempt in: /lib64/libc-2.3.2.so, fffff95557260000-fffff955572c0000 00100000
PAX: terminating task: /root/test1(test1):10737, uid/euid: 0/0, PC: fffff955572bb01c, SP: 000004464c777830
PAX: bytes at PC: 250003ff 9de3bf40 213ffffe 2315bd3b a0142155

Doing either a chpax -m or -p will allow the executable to run, but this isn't really an optimal solution. Any ideas?

-Aaron

androsyn wrote:It appears that PAX with PAGEEXEC enabled on sparc64 seems to cause issues for 64bit dynamically linked executables:

PAX: From 127.0.0.1: execution attempt in: /lib64/libc-2.3.2.so, fffff95557260000-fffff955572c0000 00100000
PAX: terminating task: /root/test1(test1):10737, uid/euid: 0/0, PC: fffff955572bb01c, SP: 000004464c777830
PAX: bytes at PC: 250003ff 9de3bf40 213ffffe 2315bd3b a0142155

the sparc64 64-bit userland is not really supported, there're a few PLT stubs that are not emulated. is it really important that you run 64 bit apps? you're the first one to complain about this, that's why i'm asking, i take it that it's not the typical use case of sparc64 . the real solution would be to get rid of the runtime generated PLT but noone volunteered so far.