linux-kernel - Re: [PATCH v4] sched/core: Use zero length to reset cpumasks in sched

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: <20231004094330.GL1539@noisy.programming.kicks-ass.net>
Date:   Wed, 4 Oct 2023 11:43:30 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Waiman Long <longman@...hat.com>, Ingo Molnar <mingo@...hat.com>,
        Juri Lelli <juri.lelli@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
        Daniel Bristot de Oliveira <bristot@...hat.com>,
        Valentin Schneider <vschneid@...hat.com>,
        linux-kernel@...r.kernel.org, Phil Auld <pauld@...hat.com>,
        Brent Rowsell <browsell@...hat.com>,
        Peter Hunt <pehunt@...hat.com>,
        Florian Weimer <fweimer@...hat.com>
Subject: Re: [PATCH v4] sched/core: Use zero length to reset cpumasks in
 sched_setaffinity()

On Wed, Oct 04, 2023 at 11:23:41AM +0200, Ingo Molnar wrote:

> >  	if (user_mask) {
> > -		cpumask_copy(user_mask, in_mask);
> > +		/*
> > +		 * All-set user cpumask resets affinity and drops the explicit
> > +		 * user mask.
> > +		 */
> > +		cpumask_and(user_mask, in_mask, cpu_possible_mask);
> > +		if (cpumask_equal(user_mask, cpu_possible_mask)) {
> > +			kfree(user_mask);
> > +			user_mask = NULL;
> > +		}
> 
> Question: is there any observable behavioral difference between current 
> (old) all-set cpumask calls and the patched (new) one?

Very little I think -- the main difference is that we no longer carry
the ->user_cpus_ptr mask around, and that saves a little masking.