Page 1 of 1

PAX: execution attempt in: <stack> (wpa_actiond)

PostPosted: Mon Nov 16, 2015 9:15 am
by Fuxino
When I shutdown my notebook I get this warning:
Code: Select all
kernel: PAX: execution attempt in: <stack>, 3f5e7a8e000-3f5e7aaf000 3fffffde000
kernel: PAX: terminating task: /usr/bin/wpa_actiond(wpa_actiond):603, uid/euid: 0/0, PC: 000003f5e7aadf14, SP: 000003f5e7aad478
kernel: PAX: bytes at PC: 41 bb 50 2f 40 00 49 ba 70 dc aa e7 f5 03 00 00 49 ff e3 90
kernel: PAX: bytes at SP-8: 0000037dd7b37598 0000037dd7b5e680 0000000000000001 0000000000000000 0000000000000000 0000000000000002 0000000000000000 000003f5e7aada60 0000000000000000 000003f5e7aadc78 0000000000000246

Is it something I should be worried about? Everything seems to work fine.

Re: PAX: execution attempt in: <stack> (wpa_actiond)

PostPosted: Mon Nov 16, 2015 9:24 am
by PaX Team
it's a gcc nested function trampoline by the look of it. you'll have to enable EMUTRAMP in the kernel and on the wpa_actiond binary and perhaps ask upstream why in 2015AD they're still using such arcane and pointless code constructs ;).

Re: PAX: execution attempt in: <stack> (wpa_actiond)

PostPosted: Tue Nov 17, 2015 4:12 pm
by Fuxino
PaX Team wrote:it's a gcc nested function trampoline by the look of it. you'll have to enable EMUTRAMP in the kernel and on the wpa_actiond binary

Looks like that was it, now I'm not getting the error anymore. :D Thanks.

Re: PAX: execution attempt in: <stack> (wpa_actiond)

PostPosted: Fri Nov 20, 2015 11:25 am
by strcat
FWIW, avoiding netctl/wpa_actiond is probably a good idea. They aren't really maintained anymore. You are much better off using connman (or even NetworkManager).

Re: PAX: execution attempt in: <stack> (wpa_actiond)

PostPosted: Tue Nov 24, 2015 7:23 am
by Fuxino
strcat wrote:FWIW, avoiding netctl/wpa_actiond is probably a good idea. They aren't really maintained anymore. You are much better off using connman (or even NetworkManager).

Thanks for the tip, I'm trying connman and it seems to work fine. :D