grsecurity forums

I'm getting a crash screenshot on boot.

This is a Debian 7.0 box, but the kernel itself was combined on an Ubuntu box.
GNU LD 2.22 was used for the compilation, as well as gcc 4.6.3.

Relevant files (vmlinux, .config, system.map) are here.

Here is the CPU the box has:

Code: Select all

micro:~> cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Celeron(R) M processor          900MHz
stepping        : 6
microcode       : 0x18
cpu MHz         : 630.024
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bts
bogomips        : 1260.04
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 32 bits virtual
power management:


Please let me know if I can provide more information.

this happened in a module and i guess we can't get that info easily so my suggestion would be to temporarily compile everything into the kernel and get a report for that.

Will do, thanks PaX Team.

Annoying enough - with everything compiled into the kernel and not using initrd, it boots.

Any suggestions?

well, you can try either of two things: binary search for the module or disable the kernel lockout feature and hope that you can boot into userland and get /proc/modules so that we can determine which module it was.

Hi tjh,

I will have this fixed in the next patch. The copy is likely from the .rodata of a module which gets rolled into the module's RX area that I was disallowing copies to/from with USERCOPY.

-Brad

Thanks, can confirm the latest patch fixes the issues.

Much appreciated!