problem after update from 2.6.26.2-grsec to 2.6.26.3-grsec

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

problem after update from 2.6.26.2-grsec to 2.6.26.3-grsec

Postby coderx » Tue Aug 26, 2008 3:23 pm

with 2.6.26.2-grsec all was fine
i just copied old config compiled the kernel and after reboot this :
invalid opcode: 0000 [#1] SMP
Modules linked in: ipv6 pcmcia pcmcia_core 8250_pnp 8250 serial_core parport_pc parport ohci_hcd thermal processor thermal_sys evdev dcdbas

Pid: 2882, comm: named Not tainted (2.6.26.3-grsec #1)
EIP: 0060:[<c0b1fe78>] EFLAGS: 00210297 CPU: 3
EAX: 00000001 EBX: ef34a5a8 ECX: 00000001 EDX: ef252f68
ESI: a6978a50 EDI: ee542920 EBP: 00000004 ESP: ef252f40
DS: 0068 ES: 0068 FS: 00d8 GS: 0033 SS: 0068
Process named (pid: 2882, ti=ef252000 task=ee542920 task.ti=ef252000)
Stack: ef34a5a8 c0812c6f ef252f68 ef34a570 a556e368 a69fd510 00000000 c0812b01
a556dbf8 c0b1ee95 a69fd510 a556dd18 a3368008 00000000 a336a008 a556dbf8
a33700c0 0020007b a556007b a5560000 ffffffff a6978a50 00000073 00210246
Call Trace:
[<c0812c6f>] <0> [<c0812b01>] <0> [<c0b1ee95>] <0> [<c0801371>] <0> [<c0802c68>] <0> =======================
Code: d1 ff f0 ff 0d 00 32 cb c0 e9 00 38 d1 ff f0 ff 0d 00 32 cb c0 e9 49 39 d1 ff f0 ff 46 08 e9 49 39 d1 ff f0 ff 08 e9 c5 e2 ff ff <f0> 83 e9 01 e9 fa 47 d1 ff 89 10 e9 c7 e2 ff ff 89 10 e9 26 48
EIP: [<c0b1fe78>] SS:ESP 0068:ef252f40
---[ end trace 55f6b3c629dfc99e ]---
invalid opcode: 0000 [#2] SMP
Modules linked in: iptable_filter ip_tables ipv6 pcmcia pcmcia_core 8250_pnp 8250 serial_core parport_pc parport ohci_hcd thermal processor thermal_sys evdev dcdbas

Pid: 3163, comm: mysqld Tainted: G D (2.6.26.3-grsec #1)
EIP: 0060:[<c0b1fe78>] EFLAGS: 00210297 CPU: 0
EAX: 00000001 EBX: ef34a760 ECX: 00000001 EDX: e9c21f50
ESI: a6829000 EDI: ef968490 EBP: 00000006 ESP: e9c21f28
DS: 0068 ES: 0068 FS: 00d8 GS: 0033 SS: 0068
Process mysqld (pid: 3163, ti=e9c21000 task=ef968490 task.ti=e9c21000)
Stack: ef34a760 c0812c6f e9c21f50 ef34a728 00000001 acb18898 0000fffe c0812b01
a9a7cbf8 c0b1ee95 acb18898 000038e1 0000fffe 0000fffe a6829000 a9a7cbf8
00000000 0004007b a680007b c0b10000 ffffffff ac82419f 00000073 00210207
Call Trace:
[<c0812c6f>] <0> [<c0812b01>] <0> [<c0b1ee95>] <0> [<c0b10000>] <0> [<c0801371>] <0> [<c0802c68>] <0> =======================
Code: d1 ff f0 ff 0d 00 32 cb c0 e9 00 38 d1 ff f0 ff 0d 00 32 cb c0 e9 49 39 d1 ff f0 ff 46 08 e9 49 39 d1 ff f0 ff 08 e9 c5 e2 ff ff <f0> 83 e9 01 e9 fa 47 d1 ff 89 10 e9 c7 e2 ff ff 89 10 e9 26 48
EIP: [<c0b1fe78>] SS:ESP 0068:e9c21f28
---[ end trace 55f6b3c629dfc99e ]---

# cat /etc/slackware-version
Slackware 12.1.0
# uname -a
Linux ns 2.6.26.3-grsec #1 SMP Tue Aug 26 21:58:16 EEST 2008 i686 Intel(R) Xeon(TM) CPU 2.00GHz GenuineIntel GNU/Linux
how can i fix this ?
coderx
 
Posts: 37
Joined: Tue Mar 25, 2008 3:57 am

Re: problem after update from 2.6.26.2-grsec to 2.6.26.3-grsec

Postby PaX Team » Tue Aug 26, 2008 5:33 pm

coderx wrote:with 2.6.26.2-grsec all was fine
i just copied old config compiled the kernel and after reboot this :
invalid opcode: 0000 [#1] SMP
can you send me or upload your bzImage/vmlinux/System.map/.config please?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: problem after update from 2.6.26.2-grsec to 2.6.26.3-grsec

Postby coderx » Tue Aug 26, 2008 6:36 pm

coderx
 
Posts: 37
Joined: Tue Mar 25, 2008 3:57 am

Re: problem after update from 2.6.26.2-grsec to 2.6.26.3-grsec

Postby PaX Team » Tue Aug 26, 2008 7:25 pm

coderx wrote:http://dc.techno-lt.org/kernel/
thanks, fixed in test17, grsec will follow soon.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity support