grsecurity forums

Hello,

I have tried the latest grsec kernel snapshot on two Debian systems (one sarge/stable and one sid/unstable) both with vanilla 2.6.17.3 with grsec patch. They both kernel panic before the end of the boot when they are trying to use ntpdate to sync up their clock.

I have put online my kernel configuration (this is from a Dell PowerEdge 2450 SMP box) : http://frlinux.net/kernel_26xx_grsec.txt

Thanks in advance
Steph

Do you have the oops report with symbols? Also, what's the date/time of the patch you were using?

-Brad

spender wrote:Do you have the oops report with symbols? Also, what's the date/time of the patch you were using?

-Brad

Sorry about that, here are two screenshots of the kernel panic :
http://frlinux.net/grsec_26173_ooops_1.jpg
http://frlinux.net/grsec_26173_ooops_2.jpg

I used this patch : grsecurity-2.1.9-2.6.17.3-200607051719.patch

Steph

FRLinux wrote:I used this patch : grsecurity-2.1.9-2.6.17.3-200607051719.patch

I also tried your latest patch posted this morning, with the same result.

Steph

FRLinux wrote:Sorry about that, here are two screenshots of the kernel panic :
http://frlinux.net/grsec_26173_ooops_1.jpg
http://frlinux.net/grsec_26173_ooops_2.jpg

unfortunately this is not enough, enable CONFIG_KALLSYMS at least to get some symbolic info. next, what happens if you enable MPROTECT? i also released a new PaX test patch, could you give it a try (with your current config then with MPROTECT)?