observed since 3.17.1-r1 , when pppd is started for ADSL link, ooops in vmalloc occurs and box freezes, exclusive to 32bit hardened x86, older 3.16 no problem, seems introduced in 3.17 line Reproducible: Always
3.17.3 is out, tested and still no change... oops when pppd is starting up...
Alex, can you please paste a copy of the OOPS message so we can try to see what causes the issue?
(In reply to Francisco Blas Izquierdo Riera from comment #2) > Alex, can you please paste a copy of the OOPS message so we can try to see > what causes the issue? Actually, in addition to the oops, can you please give us the config file as well. Upstream will probably want your vmlinuz file. This may be related to bug #510788 which also causes WARN in netwoking, but that was in 3.14.3-r1.
Created attachment 390058 [details] Ooops message Opps message and panic text from console
Created attachment 390060 [details] Kernel config
Please drop me a note when vmlinuz is needed, where to put/send... Thanks for investigating!
can you produce an oops with frame pointers enabled please?
Tested 3.17.4 with enabled frame pointers to trigger the requested Ooops. It is running fine so far without issues... the problem seems to bee gone. I assume you were already successful in tracking down the issue and this is already fixed by intention in 3.17.4 ... If not and this is just a coincidence and you still need something for further digging, please drop me a note again. Thanks to all involved for their work!
i didn't fix anything so if you get an oops, post it please.
Created attachment 390274 [details] Ooops with frame pointer enabled in kconfig
Here's the fix that was backported to 3.17.4 that resolved the issue: https://lkml.org/lkml/2014/11/7/316 -Brad
(In reply to Brad Spengler from comment #11) > Here's the fix that was backported to 3.17.4 that resolved the issue: > https://lkml.org/lkml/2014/11/7/316 > > -Brad Brad, did you backport this to grsecurity-3.0-3.17.4-201411260107? If so, then this fix is in the tree with hardened-sources-3.17.4-r1.
the fix is in upstream 3.17.4 itself.
This should be now in hardened-sources-3.17.6 which is in the tree.