linux-kernel - Re: Call Trace when adding vCPU to guest

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: Wed, 10 Apr 2024 19:29:43 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info>
Cc: LKML <linux-kernel@...r.kernel.org>, xiangfeix.ma@...el.com, Dongli
 Zhang <dongli.zhang@...cle.com>, Linux kernel regressions list
 <regressions@...ts.linux.dev>
Subject: Re: Call Trace when adding vCPU to guest

On Wed, Apr 10 2024 at 18:25, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 10.04.24 16:52, Thomas Gleixner wrote:
> I can reproduce as well. But the callstack is different. It finally
> reaches at topo_set_cpuids().

That looks about right.

> I am not able to reproduce with the below:
>
> x86/topology: Don't update cpu_possible_map in topo_set_cpuids()
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=a9025cd1c673a8d6eefc79d911075b8b452eba8f

Yes, that's the fix for the crash you saw.