grsecurity forums

Hi,

I am running several systems with Linux kernel 2.4.27 and GRSec 2.0.1.

Since one of the new systems is a P4-based hardware, I added SMP-support to my kernel and distributed it to the P4-system and some Celeron systems. Select CPU in the kernel on all systems is "Pentium III".

On the systems running no SMP-kernel everything seems to be fine, but the SMP-enabled systems stop logging after some days; no grsec messages appear in the system log anymore.

And there are some strange log lines:

kernel: /bh[:50]id:0 g/ed:0
kernel: ];RG1

Some SMP-kernel-based-systems stopped logging completely, others stopped only logging grsec-messages...

Is there anything to consider when using GRsec with P4-HT-CPUs?

Thanks

Do you have multiple P4 HT processors, or just a single P4 HT processor?

-Brad

Hi Brad,

there is only one P4-HT-CPU.

Yesterday the system crashed again with a kernel oops saying "unable to handle paging request" so it might not be grsec-related...

I built an absolute minimalistic kernel to make sure that it is not a hardware problem. If the system crashes again, I guess it is a hardware problem. If it does not crash, I will enable all additional features step by step (grsec being the first, then 4g-support, then highmem-i/o, then iptables, then library functions and so on...

I will post again as soon as I have grsec activated again.

Thanks

ohter smp problem:

ksymoops 2.4.9 on i686 2.4.26-andrews38-smp4g. Options used
-V (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.26-andrews38-smp4g/ (default)
-m /boot/System.map-2.4.26-andrews38-smp4g (specified)

kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008
kernel: c0396f6a
kernel: *pde = 00000000
kernel: Oops: 0000
kernel: CPU: 0
kernel: EIP: 0010:[gr_handle_exec_args+422/895] Not tainted
kernel: EFLAGS: 00010282
kernel: eax: 00000000 ebx: 08108010 ecx: f7592220 edx: c8902000
kernel: esi: 0000002a edi: 00000014 ebp: dfafbdc4 esp: dfafbd4c
kernel: ds: 0018 es: 0018 ss: 0018
kernel: Process exim4 (pid: 3881, stackpage=dfafb000)
kernel: Stack: c1c1de60 c890225a 0000516b 00000008 00000008 00000008 00000008 00000000
kernel: e122cca0 dfafbe64 080f0546 08108034 00000003 250000e0 7273752f 6962732f
kernel: 78652f6e 20346d69 20634d2d 76514331 302d6f65 51353030 47502d42 00000020
kernel: Call Trace: [do_execve+623/960] [timer_bh+54/980] [bh_action+76/140] [tasklet_hi_action+103/160] [do_softirq+125/220]
kernel: Code: 8b 40 08 50 e8 a1 53 00 00 83 c4 08 eb 05 b8 00 ef 42 c0 ba
Using defaults from ksymoops -t elf32-i386 -a i386


>>ecx; f7592220 <_end+371464b8/384c32f8>
>>edx; c8902000 <_end+84b6298/384c32f8>
>>ebp; dfafbdc4 <_end+1f6b005c/384c32f8>
>>esp; dfafbd4c <_end+1f6affe4/384c32f8>

Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 8b 40 08 mov 0x8(%eax),%eax
Code; 00000003 Before first symbol
3: 50 push %eax
Code; 00000004 Before first symbol
4: e8 a1 53 00 00 call 53aa <_EIP+0x53aa> 000053aa Before first symbol
Code; 00000009 Before first symbol
9: 83 c4 08 add $0x8,%esp
Code; 0000000c Before first symbol
c: eb 05 jmp 13 <_EIP+0x13> 00000013 Before first symbol
Code; 0000000e Before first symbol
e: b8 00 ef 42 c0 mov $0xc042ef00,%eax
Code; 00000013 Before first symbol
13: ba 00 00 00 00 mov $0x0,%edx