grsecurity forums

Hi,

I gave the new CONFIG_GRKERNSEC_SETXID option a try, but it ended up in kernel panic during the system startup process, somewhere in the middle of configuring network interfaces or so. Here goes the panic screenshot, if it's of any help:



The screenshot has been captured on a (nearly) vanilla 2.6.32.56 with grsecurity-2.2.2-2.6.32.56-201202032051.patch applied. It also crashes with grsecurity-2.2.2-2.6.32.56-201202051926.patch and 100% vanilla 2.6.32.56 (sorry, no more screenshots ). Without CONFIG_GRKERNSEC_SETXID the system booted happily as usual.

Thanks for the report. I'll try to have it fixed tonight.

-Brad

It should be fixed in the latest patch I uploaded.

Thanks,
-Brad

Hi,

Sorry, I was not able to test it till now. I confirm that 2.6.32.56 + grsecurity-2.2.2-2.6.32.56-201202071726.patch now boots fine with CONFIG_GRKERNSEC_SETXID=y. Thank you