grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

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

grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

Postby coderx » Thu Aug 09, 2012 3:44 pm

Last edited by coderx on Fri Aug 10, 2012 3:17 am, edited 2 times in total.
coderx
 
Posts: 37
Joined: Tue Mar 25, 2008 3:57 am

Re: grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

Postby PaX Team » Thu Aug 09, 2012 5:48 pm

unfortunately this is not enough information, we'll need the logs of the first oops, kernel config, kernel images, etc.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

Postby coderx » Fri Aug 10, 2012 3:16 am

same result with grsecurity-2.9.1-3.5.1-201208091728.patch

btw its vm running on vmware workstation
gcc version 4.7.1 (Debian 4.7.1-2)
Distributor ID: Debian
Description: Debian GNU/Linux testing (wheezy)
Release: testing
Codename: wheezy
with 3.4.6 patch i dont have any problems

http://s8.postimage.org/4utich7np/Other ... _10_01.png
http://www.sendspace.com/file/vnc9b3
coderx
 
Posts: 37
Joined: Tue Mar 25, 2008 3:57 am

Re: grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

Postby PaX Team » Fri Aug 10, 2012 6:13 am

i tried your config with a PaX only patch and can't reproduce the modprobe triggered problem, so could you give PaX itself a try? you can also enable serial console support and add a serial device to vmware to log the kernel messages to a file, that'd be very helpful.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: grsecurity-2.9.1-3.5.0-201208081934.patch kernel oops

Postby PaX Team » Fri Sep 07, 2012 3:14 pm

i've just fixed a KERNEXEC/MODULES related problem on i386 for 3.5, can you test it please?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity support

cron