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: <a4cb5e3e-717e-4a86-9e15-5b14ef322314@intel.com>
Date: Wed, 13 Aug 2025 09:41:48 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Oleg Nesterov <oleg@...hat.com>, Borislav Petkov <bp@...en8.de>,
 Dave Hansen <dave.hansen@...ux.intel.com>, Ingo Molnar <mingo@...nel.org>,
 "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
 Thomas Gleixner <tglx@...utronix.de>, Jens Axboe <axboe@...nel.dk>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: PF_USER_WORKERs and shadow stack

On 8/13/25 09:28, Oleg Nesterov wrote:
> But it seems that if a features_enabled(ARCH_SHSTK_SHSTK) thread creates a
> PF_USER_WORKER thread, shstk_alloc_thread_stack() will allocate the shadow
> stack for no reason.

Is this costing us anything other than some CPU cycles and 160 bytes of
memory for a VMA?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ