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] [thread-next>] [day] [month] [year] [list]
Message-ID: <d28c9690341715fff04fbc01fd80723a30195f23.camel@sipsolutions.net>
Date: Wed, 10 Sep 2025 13:59:02 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Tiwei Bie <tiwei.bie@...ux.dev>, richard@....at, 
	anton.ivanov@...bridgegreys.com
Cc: linux-um@...ts.infradead.org, linux-kernel@...r.kernel.org, 
	benjamin@...solutions.net, arnd@...db.de, tiwei.btw@...group.com
Subject: Re: [PATCH v2 03/10] um: vdso: Implement __vdso_getcpu() via syscall

On Sun, 2025-08-10 at 13:51 +0800, Tiwei Bie wrote:
> From: Tiwei Bie <tiwei.btw@...group.com>
> 
> We are going to support SMP in UML, so we can not hard code
> the CPU and NUMA node in __vdso_getcpu() anymore.

Correct. But does that mean we actually have to implement it via syscall
in the VDSO? That seems a bit odd? ARM doesn't seem to have getcpu in
the VDSO at all, for example, so could we do the same and just remove
it?

johannes

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ