linux-kernel - Re: [PATCH] workqueue: respect isolated cpus when queueing an unbound work

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: <20171021161533.GQ1302522@devbig577.frc2.facebook.com>
Date:   Sat, 21 Oct 2017 09:15:33 -0700
From:   Tejun Heo <tj@...nel.org>
To:     Tal Shorer <tal.shorer@...il.com>
Cc:     jiangshanlai@...il.com,
        "<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] workqueue: respect isolated cpus when queueing an
 unbound work

Hello,

On Sat, Oct 21, 2017 at 07:13:33PM +0300, Tal Shorer wrote:
> > Do we have a consistent behavior around this?  Are there different
> > examples where isolcpus interact with other dynamically configurable
> > parameters?
> >
> sched_setaffinity comes to mind, which obviously bypasses isolcpus.
> Running git grep, other uses of cpu_isolated_map are just its
> initialization and its use and the initialization of
> non_isolated_cpus.

Can you add a comment explaining that it's intentional that we only
follow isolcpus during boot and allow later overrides?

Thanks.

-- 
tejun