| 1 |
Brian Kroth wrote: |
| 2 |
> pageexec@××××××××.hu wrote: |
| 3 |
>> On 4 Nov 2007 at 1:30, Brian Kroth wrote: |
| 4 |
>> |
| 5 |
>>> No problems after 20+ minutes of looping the command. So SEGMEXEC |
| 6 |
>>> seems to be the culprit, correct? |
| 7 |
>> |
| 8 |
>> yes, and i as wrote earlier, most likely the vma mirroring part. |
| 9 |
>> |
| 10 |
>>> Did something change in the way that was handled from 2.6.20 to 2.6.22? |
| 11 |
>> |
| 12 |
>> yes, i rewrote vma mirroring (the core concept behind the implementation |
| 13 |
>> of SEGMEXEC) in july. |
| 14 |
>> |
| 15 |
> |
| 16 |
> More problems found when I left cactid and nagios with paxctl -s. That |
| 17 |
> didn't seem to solve everything for nagios, and cacti is no getting |
| 18 |
> killed by grsec for some reason. Where can I increase the logging level |
| 19 |
> like you mentioned? |
| 20 |
> |
| 21 |
> Thanks, |
| 22 |
> Brian |
| 23 |
> |
| 24 |
> |
| 25 |
> Nov 4 02:00:46 tux-mc Bad page state in process 'nagios' |
| 26 |
> Nov 4 02:00:46 tux-mc page:c178b0c0 flags:0x80000001 mapping:00000000 |
| 27 |
> mapcount:0 count:0 |
| 28 |
> Nov 4 02:00:46 tux-mc Trying to fix it up, but a reboot is needed |
| 29 |
> Nov 4 02:00:46 tux-mc Backtrace: |
| 30 |
> Nov 4 02:00:46 tux-mc [<c0403da8>] show_trace_log_lvl+0x1a/0x30 |
| 31 |
> Nov 4 02:00:46 tux-mc [<c0403dd0>] show_trace+0x12/0x14 |
| 32 |
> Nov 4 02:00:46 tux-mc [<c0403eca>] dump_stack+0x16/0x18 |
| 33 |
> Nov 4 02:00:46 tux-mc [<c044ba59>] bad_page+0x66/0x97 |
| 34 |
> Nov 4 02:00:46 tux-mc [<c044c52e>] free_hot_cold_page+0x71/0x180 |
| 35 |
> Nov 4 02:00:46 tux-mc [<c044c647>] free_hot_page+0xa/0xc |
| 36 |
> Nov 4 02:00:46 tux-mc [<c044ef70>] __page_cache_release+0x84/0x90 |
| 37 |
> Nov 4 02:00:46 tux-mc [<c044efdc>] put_page+0x27/0x36 |
| 38 |
> Nov 4 02:00:46 tux-mc [<c04558aa>] do_wp_page+0x219/0x3fc |
| 39 |
> Nov 4 02:00:46 tux-mc [<c0456b37>] __handle_mm_fault+0x277/0x2cd |
| 40 |
> Nov 4 02:00:46 tux-mc [<c0414406>] do_page_fault+0x1cd/0x7bf |
| 41 |
> Nov 4 02:00:46 tux-mc [<c06e6d55>] error_code+0x75/0x80 |
| 42 |
> Nov 4 02:00:46 tux-mc ======================= |
| 43 |
> |
| 44 |
> Nov 4 05:30:02 tux-mc grsec: signal 11 sent to |
| 45 |
> /usr/sbin/cactid[cactid:12039] uid/euid:81/81 gid/egid:81/81, parent |
| 46 |
> /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 |
| 47 |
> Nov 4 05:45:06 tux-mc grsec: signal 11 sent to |
| 48 |
> /usr/sbin/cactid[cactid:13347] uid/euid:81/81 gid/egid:81/81, parent |
| 49 |
> /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 |
| 50 |
> Nov 4 06:35:03 tux-mc grsec: signal 11 sent to |
| 51 |
> /usr/sbin/cactid[cactid:17502] uid/euid:81/81 gid/egid:81/81, parent |
| 52 |
> /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 |
| 53 |
> |
| 54 |
|
| 55 |
Nevermind about what I said about nagios - I had put the wrong path into |
| 56 |
/etc/conf.d/chpax. The grsec messages still hold though. |
| 57 |
2.6.23-hardened-r1 is building now with your patch. Do you want me to |
| 58 |
turn on some of the lock debugging options in debug kernel? |
| 59 |
|
| 60 |
Brian |
Archives