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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260107112835.GBaV5DY1sc3HeLKINb@fat_crate.local>
Date: Wed, 7 Jan 2026 12:28:35 +0100
From: Borislav Petkov <bp@...en8.de>
To: Xiaoyao Li <xiaoyao.li@...el.com>
Cc: Rong Zhang <i@...g.moe>, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
	"H. Peter Anvin" <hpa@...or.com>, Fenghua Yu <fenghuay@...dia.com>,
	linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH] x86/split_lock: Zap the unwieldy switch-case in
 sld_state_show()

On Wed, Jan 07, 2026 at 01:38:41PM +0800, Xiaoyao Li wrote:
> For fatal mode, there is no such handling of temporarily disabling the
> feature and we don't need the CPU offline callback.

Yah, I got that. But why?

Why is fatal mode different?

Why does it matter what the split lock mode is when we offline CPUs?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ