linux-kernel - Re: [LKP] [x86/pci] 7ffb31888c: PANIC:early

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]

Date:   Sun, 23 Sep 2018 18:05:06 +0800
From:   Pu Wen <puwen@...on.cn>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Rong Chen <rong.a.chen@...el.com>, bp@...en8.de, mingo@...hat.com,
        hpa@...or.com, x86@...nel.org, thomas.lendacky@....com,
        helgaas@...nel.org, linux-kernel@...r.kernel.org,
        linux-arch@...r.kernel.org, linux-pci@...r.kernel.org, lkp@...org
Subject: Re: [LKP] [x86/pci] 7ffb31888c: PANIC:early_exception

On 2018/9/20 17:39, Thomas Gleixner wrote:
>> I reproduced the PANIC by running lkp-tests with a Intel machine.
>>
>> The reason is that the function early_is_amd_nb is called even if
>> running on Intel machine. At this case the misc_ids is NULL so the
>> PANIC occur.
>>
>> I'll rework a patch to solve this problem, either restore the default
>> value of misc_ids with the original AMD one or not call early_is_amd_nb
>> on Intel platform.
> 
> Return when !AMD and !HYGON is the right thing to do. No point in checking
> device ids which cannot happen in the first place.

All right, I reworked a new reversion which will return if it's Intel.

Thanks,
Pu Wen