425536 – Kernel panic in sys-kernel/hardened-sources-3.4.2-r1

Bug 425536 - Kernel panic in sys-kernel/hardened-sources-3.4.2-r1

Summary: Kernel panic in sys-kernel/hardened-sources-3.4.2-r1

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	The Gentoo Linux Hardened Kernel Team (OBSOLETE)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-07-09 19:59 UTC by Richard Ostrow
Modified:	2012-08-25 21:28 UTC (History)
CC List:	5 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
last 64 kb of console output before panic (crashlog.log,64.10 KB, text/plain) 2012-07-09 19:59 UTC, Richard Ostrow	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Richard Ostrow 2012-07-09 19:59:34 UTC

Created attachment 317730 [details]
last 64 kb of console output before panic

I'm experiencing a kernel panic with 3.4.2-r1 on one machine. It just so happens that this machine has a serial console with the other end running a screen session, so the last 64 kb of this panic were recorded (see attached). This panic occurs within one hour of booting this kernel (happened twice before I reverted back to hardened-sources-3.2.11). Using 3.2.11, there appear to be no such issues. I also have two other machines running 3.4.2-r1 without any issues (been running a couple of days now).

Biggest kernel-related difference I could think of is that this is my NFS4 server utilizing sec=krb5[ip]. Otherwise, not sure what could be affecting things at the kernel level.

Comment 1 Göktürk Yüksek archtester

2012-07-09 20:56:59 UTC

There seems to be an NFSv4 regression in 3.4.2 according to this link [0]. I couldn't see anything useful in the kernel log, maybe somebody else would. You may rmmod nfsd to see if you can isolate it. Or you may choose the painful way, get 3.4.2 from git sources and bisect it until you find the offending comment. Anyway, it would certainly help if you can capture the first oops somehow.

[0] http://www.spinics.net/lists/linux-nfs/msg30898.html

Comment 2 Anthony Basile gentoo-dev

2012-07-10 17:31:35 UTC

These are not the same oopses.  Yours is not due to nfsv4, at least not directly.  Can you try the latest patches?  I'll be adding them to the tree later today.

@spender, pipacs, this is grsecurity-2.9.1-3.4.3-201206171836

Comment 3 Göktürk Yüksek archtester

2012-07-10 17:58:11 UTC

(In reply to comment #2)
> These are not the same oopses.
The first oops in the log is Oops: 0000 [#123], maybe the first one had nfs in the stack ...

Comment 4 PaX Team 2012-07-10 19:26:35 UTC

we'd need to see the first oops, would it be possible to capture it? also try something more recent like 3.4.4 and latest grsec please ;).

Comment 5 Anthony Basile gentoo-dev

2012-07-11 03:50:55 UTC

(In reply to comment #4)
> we'd need to see the first oops, would it be possible to capture it? also
> try something more recent like 3.4.4 and latest grsec please ;).

The following are based of the very latest grsec patches:

hardened-sources-3.4.4-r2 => grsecurity-2.9.1-3.4.4-201207080925

hardened-sources-3.2.22 => grsecurity-2.9.1-3.2.22-201207080924

hardened-sources-2.6.32-r114 => grsecurity-2.9.1-2.6.32.59-201207080923

Comment 6 Anthony Basile gentoo-dev

2012-07-28 23:17:35 UTC

Is this still an issue in the latest kernels?

Comment 7 Richard Ostrow 2012-08-25 15:30:38 UTC

Doesn't appear to be an issue with sys-kernel/hardened-sources-3.4.5