2.6.18-grsec = init SIGSEGV
Posted: Thu Oct 26, 2006 7:16 pmI tried a few different versions of grsec with 2.6.18 and 2.6.18.1 and all give me init's SIGSEGV while booting.
If I enable signal logging, I can see:
I tried to narrow it to specific grsec options and it seems grsec patch itself does it, even with no grsec options enabled (!)
I verified it the following way:
1) got a clean vanilla kernel
2) compiled it with my .config
3) booted - it runned just fine
4) patched this kernel with newest stable grsec (I needed to resolve trivial conflicts by hand; I also tried the version from paxguy1 - no difference)
5) "make oldconfig" and "N" to all grsec questions
6) compiled
7) reboot - hangs after "Freeing unused kernel memory"
I guess it was init sigsegv-ing, but with no grsec signal logging I couldn't see that.
Oh, and grsec for 2.6.17 worked just fine!
What can be the cause?
If I can help to in some way (show my .config, try out some configurations), please tell me!
If I enable signal logging, I can see:
- Code: Select all
(...)
Freeing unused kernel memory: (...)
grsec: signal 11 sent to /sbin/init [init:1] uid/euid:0/0 gig/egid:0/0, parent /[swapper:0] uid/gid:0/0 gid/egid:0/0
(...and lots of it)
I tried to narrow it to specific grsec options and it seems grsec patch itself does it, even with no grsec options enabled (!)
I verified it the following way:
1) got a clean vanilla kernel
2) compiled it with my .config
3) booted - it runned just fine
4) patched this kernel with newest stable grsec (I needed to resolve trivial conflicts by hand; I also tried the version from paxguy1 - no difference)
5) "make oldconfig" and "N" to all grsec questions
6) compiled
7) reboot - hangs after "Freeing unused kernel memory"
I guess it was init sigsegv-ing, but with no grsec signal logging I couldn't see that.
Oh, and grsec for 2.6.17 worked just fine!
What can be the cause?
If I can help to in some way (show my .config, try out some configurations), please tell me!