linux-kernel - Re: Lockdep warning with init_espfix

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: <543E9B4B.9040608@zytor.com>
Date:	Wed, 15 Oct 2014 09:05:31 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Prarit Bhargava <prarit@...hat.com>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: Lockdep warning with init_espfix_ap()

On 10/15/2014 09:03 AM, Prarit Bhargava wrote:
>>
>> It is kind of a messy situation, because this code needs to allocate
>> memory but is run before the secondary CPU is fully up.  As such, it is
>> a false positive, at least in some ways.
> 
> Interesting -- FWIW, I can reproduce this 100% of the time on _one_ system.  It
> isn't a big deal and likely just worth noting at this point.  I *always* see it
> when bringing up CPU 64 (of 128).
> 

... because that is the first CPU which needs to allocate memory.

	-hpa

--
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/