linux-kernel - Re: [PATCH 00/19] sched: Core Scheduling

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: <YIGyeVBS0qnes/RP@hirez.programming.kicks-ass.net>
Date:   Thu, 22 Apr 2021 19:29:29 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Don Hiatt <dhiatt@...italocean.com>
Cc:     Joel Fernandes <joel@...lfernandes.org>,
        "Hyser,Chris" <chris.hyser@...cle.com>,
        Josh Don <joshdon@...gle.com>, mingo@...nel.org,
        vincent.guittot@...aro.org, valentin.schneider@....com,
        mgorman@...e.de, linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: Re: [PATCH 00/19] sched: Core Scheduling

On Thu, Apr 22, 2021 at 09:43:59AM -0700, Don Hiatt wrote:
> On Thu, Apr 22, 2021 at 5:37 AM Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > Hai,
> >
> > This is an agressive fold of all the core-scheduling work so far. I've stripped
> > a whole bunch of tags along the way (hopefully not too many, please yell if you
> > feel I made a mistake), including tested-by. Please retest.
> >
> > Changes since the last partial post is dropping all the cgroup stuff and
> > PR_SCHED_CORE_CLEAR as well as that exec() behaviour in order to later resolve
> > the cgroup issue.
> >
> Hi Peter,
> 
> Is there a reason that PR_SCHED_CORE_CLEAR got removed? It's handy to
> be able to clear cookies.

I agree, but if we're forced to do cgroup with cookie inherit, when
CLEAR allows a trivial escape.

Until that whole cgroup thing is sorted, it is easiest to not have
CLEAR, lest we have to change/augment CLEAR semantics in unfortunate
ways, which is always harder once an API is out there.

Also, see the entire previous discussion here:

  https://lore.kernel.org/lkml/20210401131012.395311786@infradead.org/