linux-kernel - Re: [PATCH] sched_ext: Provide a per-scheduler unique sequence counter

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: <Zvru7Qx4aZ9MVU6G@slm.duckdns.org>
Date: Mon, 30 Sep 2024 08:33:17 -1000
From: Tejun Heo <tj@...nel.org>
To: Andrea Righi <andrea.righi@...ux.dev>
Cc: David Vernet <void@...ifault.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched_ext: Provide a per-scheduler unique sequence
 counter

Hello, Andrea.

On Fri, Sep 27, 2024 at 06:59:01PM +0200, Andrea Righi wrote:
...
> @@ -662,6 +662,13 @@ struct sched_ext_ops {
>  	 */
>  	u64 hotplug_seq;
>  
> +	/*
> +	 * enable_seq - unique per-scheduler counter that can be accessed from
> +	 * user-space to determine if a scheduler (within a specific hierarchy)
> +	 * has been restarted.
> +	 */
> +	s64 enable_seq;

Let's just make it a global variable for now. When we package up context for
each scheduler instance into a struct, it will get packaged up together.
It's a bit odd to add enable_seq to ops as userspace can't do anything with
it (note that hotplug_seq is different in that it's provided by the
userspace on load).

Thanks.

-- 
tejun