| 1 |
pageexec@××××××××.hu wrote: |
| 2 |
> On 4 Nov 2007 at 7:53, Brian Kroth wrote: |
| 3 |
> |
| 4 |
>>> Nov 4 05:30:02 tux-mc grsec: signal 11 sent to |
| 5 |
>>> /usr/sbin/cactid[cactid:12039] uid/euid:81/81 gid/egid:81/81, parent |
| 6 |
> |
| 7 |
> can you run cactid from commandline after you increased the coredump |
| 8 |
> limit (ulimit -c unlimited)? this way you'll get a coredump and can |
| 9 |
> examine it in gdb (the usual stuff of bt, x/8i $pc, etc). also what |
| 10 |
> were the exact PaX flags on cactid this time? |
| 11 |
|
| 12 |
tux-mc ~ # paxctl -v /usr/sbin/cactid |
| 13 |
PaX control v0.4 |
| 14 |
Copyright 2004,2005,2006 PaX Team <pageexec@××××××××.hu> |
| 15 |
|
| 16 |
- PaX flags: P-S-M--x-e-- [/usr/sbin/cactid] |
| 17 |
PAGEEXEC is enabled |
| 18 |
SEGMEXEC is enabled |
| 19 |
MPROTECT is enabled |
| 20 |
RANDEXEC is disabled |
| 21 |
EMUTRAMP is disabled |
| 22 |
|
| 23 |
Anyway to force a core dump? ulimit -c unlimited didn't seem to get me |
| 24 |
anything in /tmp or cwd, which is where I expected to see them. |
| 25 |
|
| 26 |
Nov 4 09:40:40 tux-mc Bad page state in process 'cactid' |
| 27 |
Nov 4 09:40:40 tux-mc page:c1504640 flags:0x40000001 mapping:00000000 |
| 28 |
mapcount:0 count:0 |
| 29 |
Nov 4 09:40:40 tux-mc Trying to fix it up, but a reboot is needed |
| 30 |
Nov 4 09:40:40 tux-mc Backtrace: |
| 31 |
Nov 4 09:40:40 tux-mc [<c0403e94>] show_trace_log_lvl+0x1a/0x30 |
| 32 |
Nov 4 09:40:40 tux-mc [<c0403ebc>] show_trace+0x12/0x14 |
| 33 |
Nov 4 09:40:40 tux-mc [<c0403fb6>] dump_stack+0x16/0x18 |
| 34 |
Nov 4 09:40:40 tux-mc [<c044bbd5>] bad_page+0x66/0x97 |
| 35 |
Nov 4 09:40:40 tux-mc [<c044c5c7>] free_hot_cold_page+0x71/0x176 |
| 36 |
Nov 4 09:40:40 tux-mc [<c044c6d6>] free_hot_page+0xa/0xc |
| 37 |
Nov 4 09:40:40 tux-mc [<c044f18c>] __page_cache_release+0x84/0x90 |
| 38 |
Nov 4 09:40:40 tux-mc [<c044f1f8>] put_page+0x27/0x36 |
| 39 |
Nov 4 09:40:40 tux-mc [<c0455d96>] do_wp_page+0x227/0x443 |
| 40 |
Nov 4 09:40:40 tux-mc [<c04571e3>] handle_mm_fault+0x2bc/0x2ef |
| 41 |
Nov 4 09:40:40 tux-mc [<c06f0714>] do_page_fault+0x34c/0x80a |
| 42 |
Nov 4 09:40:40 tux-mc [<c06eed65>] error_code+0x75/0x80 |
| 43 |
Nov 4 09:40:40 tux-mc ======================= |
| 44 |
|
| 45 |
> |
| 46 |
>> Nevermind about what I said about nagios - I had put the wrong path into |
| 47 |
>> /etc/conf.d/chpax. The grsec messages still hold though. |
| 48 |
>> 2.6.23-hardened-r1 is building now with your patch. Do you want me to |
| 49 |
>> turn on some of the lock debugging options in debug kernel? |
| 50 |
> |
| 51 |
> let's try one thing at a time, first i'd just like to see my printk |
| 52 |
> produce something at all ;-). |
| 53 |
|
| 54 |
Sounds good. |
Archives