linux-kernel - Re: lockdep issue booting v4.1 upstream kernel with >64 x86

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150627085631.GA27131@pd.tnic>
Date:	Sat, 27 Jun 2015 10:56:31 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Michel Lespinasse <walken@...gle.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: lockdep issue booting v4.1 upstream kernel with >64 x86_64 CPUs

On Fri, Jun 26, 2015 at 06:38:20PM -0700, Michel Lespinasse wrote:
> Hi Peter,
> 
> I am getting a minor issue trying to boot a lockdep enabled x86_64
> kernel with >64 CPUs.
> 
> The kernel boots the first 64 CPUs without issues, but then complains
> that lockdep wants to allocate memory while start_secondary ->
> init_espfix_ap has IRQs disabled:

Does that help:

https://lkml.kernel.org/r/1435311202-13248-1-git-send-email-zhugh.fnst@cn.fujitsu.com

?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/