linux-grsec-4.7.7 locks up within 30 minutes

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

Moderators: spender, PaX Team

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby foxxx0 » Fri Oct 21, 2016 5:19 pm

(without changing the config, saw the reply from spender too late)

dmesg right after boot: https://paste.foxxx0.de/47TWf/

after triggering the panic: https://paste.foxxx0.de/oke/

I will try with GRKERNSEC_KERN_LOCKOUT disabled tomorrow again.
foxxx0
 
Posts: 14
Joined: Tue Jul 12, 2016 3:03 am

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby spender » Fri Oct 21, 2016 5:26 pm

When you reboot without GRKERNSEC_KERN_LOCKOUT, can you also change the %pS to %pA ?

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm
Location: VA, USA

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby PaX Team » Fri Oct 21, 2016 7:49 pm

what's addr2line -e build_dir/vmlinux -fip ffffffff81419a98 say?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby timbgo » Sat Oct 22, 2016 4:08 am

foxxx0 wrote:Alright, so:

4.6.4.r201607112205 is working just fine

4.7.0.r201608131240 is broken

So the issue (at least for me) was introduced in 4.7.0.
Unfortunately I have no later 4.6.x kernels that I could test, so >4.6.4.r201607112205 and <= 4.7.0.r201608131240 is the range where the issue was introduced.


May be, but I'm having a likely bug in the kernel issue as well. I'm not an expert, but the symptoms are similar to your case:
banning user... until system restart for ... kernel crash w/ Qemu
viewtopic.php?f=3&t=4593#p16685

And I reported the Call Trace's quite a few.

I said "may be" above, because in my case, with Qemu in Gentoo, the last kernel that works is:
Code: Select all
sys-kernel/hardened-sources-4.7.5
(in Gentoo portage terms)
And both:
Code: Select all
sys-kernel/hardened-sources-4.7.6
and
Code: Select all
sys-kernel/hardened-sources-4.7.7
crash.
Regards!
---
Miroslav Rovis
Zagreb, Croatia
http://www.CroatiaFidelis.hr
Try refute: rootkit hooks in kernel,
linux capabilities for intrusion? (Linus?)
timbgo
 
Posts: 295
Joined: Tue Apr 16, 2013 9:34 am
Location: Zagreb, Croatia

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby foxxx0 » Sat Oct 22, 2016 4:23 am

spender wrote:When you reboot without GRKERNSEC_KERN_LOCKOUT, can you also change the %pS to %pA ?

-Brad


Building now, stay tuned.

PaX Team wrote:what's addr2line -e build_dir/vmlinux -fip ffffffff81419a98 say?


Not much, just:
Code: Select all
$ addr2line -e src/linux-4.7/vmlinux -fip ffffffff81419a98
show_type at bgrt.c:?
foxxx0
 
Posts: 14
Joined: Tue Jul 12, 2016 3:03 am

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby foxxx0 » Sat Oct 22, 2016 5:23 am

Alright, gathering information with GRKERNSEC_KERN_LOCKOUT disabled is much less annoying.

Here is the dmesg after running the grep that successfully triggered the issue in all previous tests:
https://paste.foxxx0.de/l6P9pW/
foxxx0
 
Posts: 14
Joined: Tue Jul 12, 2016 3:03 am

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby PaX Team » Sat Oct 22, 2016 5:31 am

thanks, that was enough to identify the problem, all the sysfs callbacks in drivers/acpi/bgrt.c have the wrong type, i'll fix them in the next patch. for next time, you could enable the DEBUG_INFO options ;).

@Miroslav: your problem is something unrelated, please keep that discussion in the other thread (or at https://bugs.gentoo.org/show_bug.cgi?id=597554 which is where it was already reported).
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: linux-grsec-4.7.7 locks up within 30 minutes

Postby foxxx0 » Sun Oct 23, 2016 3:11 pm

PaX Team wrote:thanks, that was enough to identify the problem, all the sysfs callbacks in drivers/acpi/bgrt.c have the wrong type, i'll fix them in the next patch. for next time, you could enable the DEBUG_INFO options ;).

@Miroslav: your problem is something unrelated, please keep that discussion in the other thread (or at https://bugs.gentoo.org/show_bug.cgi?id=597554 which is where it was already reported).


Just tested 4.7.10.r201610222037 and the issue seems to be fixed.

Thanks! Always a pleasure working with you guys :wink:
foxxx0
 
Posts: 14
Joined: Tue Jul 12, 2016 3:03 am

Previous

Return to grsecurity support

cron