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: <5592E89F.7010704@kernel.org>
Date:	Tue, 30 Jun 2015 12:06:07 -0700
From:	Andy Lutomirski <luto@...nel.org>
To:	Borislav Petkov <bp@...en8.de>,
	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 06/27/2015 03:46 AM, Borislav Petkov wrote:
> On Sat, Jun 27, 2015 at 03:32:40AM -0700, Michel Lespinasse wrote:
>> Yes, tried this successfully both with <64 and >64 CPUs, this does get
>> rid of the lockdep warning for me.
>
> Thanks, I'll add your Tested-by to the patch.
>

Just for kicks, can one of you big NUMA owners try running the sigreturn 
tests (tools/testing/selftests/x86/sigreturn_{32,64}) on one of these 
monsters with that patch applied, preferably on every cpu?

Something like:

for i in `seq 1 64`; do (taskset -c $i ./sigreturn_32 && taskset -c $i 
./sigreturn_64) >/dev/null || echo FAIL; done

I don't see why it would fail, but if the percpu conversion was botched, 
then these tests are likely to blow up.

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