Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#51398 - [linux-grsec] 1:4.7.7.r201610101902-1 panics and freezes

Attached to Project: Community Packages
Opened by Sam Stuewe (HalosGhost) - Saturday, 15 October 2016, 15:55 GMT
Last edited by Daniel Micay (thestinger) - Friday, 28 October 2016, 23:19 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Upon upgrading to linux-grsec 1:4.7.7.r201610101902-1 and rebooting, I began experiencing seemingly-random freezing. Upon further investigation, it is clear that it is a kernel panic.
Downgrading to 1:4.7.6.r201609301918-1 avoids the panics.

Steps to Reproduce:

I do not have SysRq set up, so I did not test its effectiveness.
I used hard resets to reboot.
After some more investigation, I configured tty7 to receive logs from journald and awaited a crash on tty7, but none came.
On the recommendation of a fellow Archer, I started trying to cause some system load to see if that would trigger the crash, and it did (building pacman-git caused it quite quickly)
This task depends upon

Closed by  Daniel Micay (thestinger)
Friday, 28 October 2016, 23:19 GMT
Reason for closing:  Fixed
Comment by Sam Stuewe (HalosGhost) - Saturday, 15 October 2016, 15:56 GMT
Backtrace did not get uploaded apparently, though I am not sure why. I have uploaded it to gehidore's pb instance: <https://pb.gehidore.net/AI12n2R4aUtL2LLjxCZfcRkY_ceg.jpg> (sorry for the image quality; no screenshots available)
Comment by Daniel Micay (thestinger) - Saturday, 15 October 2016, 16:27 GMT
You can add pax_size_overflow_report_only on your kernel line for now. That way it will only detect and log the overflow rather than causing a kernel panic.
Comment by Daniel Micay (thestinger) - Saturday, 15 October 2016, 17:20 GMT
Can you get another image with more context (a bit further up)?
Comment by Daniel Micay (thestinger) - Saturday, 15 October 2016, 17:26 GMT
cc PaX Team, Emese (if this silly bug tracker works)
Comment by PaX Team (paxteam) - Saturday, 15 October 2016, 22:13 GMT
we've regenerated the size overflow hash tables for the latest version of the plugin which is why a few new false positives appeared. i already fixed them in PaX and they'll be fixed in the next grsec too. if you want to play it safe(r) then disable CONFIG_PAX_SIZE_OVERFLOW_EXTRA.
Comment by Sam Stuewe (HalosGhost) - Sunday, 23 October 2016, 21:07 GMT
thestinger,

Sorry for the delay. I am afraid getting an image from higher up in the trace is difficult since the screen scrolls down and once the trace has printed, I cannot scroll as one normally does in a tty.

However, since 4.7.10 just hit testing, here's hoping this simply won't be an issue anymore.
Comment by Sam Stuewe (HalosGhost) - Friday, 28 October 2016, 22:37 GMT
Okay, with 4.7.10.201610222037-1-grsec, this issue seems to have been fixed as the PaX Team mentioned it would.

Loading...