linux-kernel - Re: smpboot seems to be confused on dual EPYC system

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: <CAEJqkgjCzgE-xKHxVLDU3dCOpwJ4P6DwOY7n9tU_xD7e_fdtYw@mail.gmail.com>
Date:   Mon, 28 May 2018 01:25:49 +0200
From:   Gabriel C <nix.or.die@...il.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: smpboot seems to be confused on dual EPYC system

2018-05-28 1:16 GMT+02:00 Borislav Petkov <bp@...en8.de>:
> On Mon, May 28, 2018 at 12:51:17AM +0200, Gabriel C wrote:
>> 128CPUs for sure not possible and for sure no way to have '2' CPUs installed.
>
> With that last "'2' CPUs" you mean, two physical processors and thus two
> sockets, right?

Yes.

>
> In any case, this info is what we've gotten from the BIOS so if that
> BIOS tells us this way...

Sure .. not the first time BIOSes lies about things :)

I never said that being an kernel bug I just noticed
something is getting confused.

>
> Again, you don't see any other issues besides the misrepresenting of max
> packages or?
>

Right no other issues.