linux-kernel - Re: [PATCH] sched/proc: Print user_cpus

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]

Date: Mon, 29 Apr 2024 14:10:00 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Xuewen Yan <xuewen.yan@...soc.com>
Cc: akpm@...ux-foundation.org, oleg@...hat.com, longman@...hat.com,
	dylanbhatch@...gle.com, rick.p.edgecombe@...el.com,
	ke.wang@...soc.com, xuewen.yan94@...il.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] sched/proc: Print user_cpus_ptr for task status

On Mon, Apr 29, 2024 at 04:46:33PM +0800, Xuewen Yan wrote:
> The commit 851a723e45d1c("sched: Always clear user_cpus_ptr in do_set_cpus_allowed()")
> would clear the user_cpus_ptr when call the do_set_cpus_allowed.
> 
> In order to determine whether the user_cpus_ptr is taking effect,
> it is better to print the task's user_cpus_ptr.

This is an ABI change and would mandate we forever more have this
distinction. I don't think your changes justifies things sufficiently
for this.