linux-kernel - mainline boot failures III: scheduler NULL pointer reference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 26 Apr 2008 16:26:34 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	mingo@...e.hu, torvalds@...l.org, linux-kernel@...r.kernel.org
Subject: mainline boot failures III: scheduler NULL pointer reference

FYI

I see lots of boot failures on various setups with current mainline
(git8, b1721d0da266b4af8cb4419473b4ca36206ab200). Unfortunately
they are all different.

All with a defconfig kernel. Haven't investigated closely yet:

This one is a recursive oops with most of the data scrolling away
and unfortunately also no serial console handy, but it's 
a NULL pointer reference in set_next_entity somewhere in the scheduler.

-Andi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/