linux-kernel - Re: [PATCH] cpuset code prevents binding tasks to new 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]

Message-ID: <20060821232738.GA11309@localdomain>
Date:	Mon, 21 Aug 2006 18:27:38 -0500
From:	Nathan Lynch <ntl@...ox.com>
To:	Paul Jackson <pj@....com>
Cc:	anton@...ba.org, simon.derr@...l.net, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH] cpuset code prevents binding tasks to new cpus

Paul Jackson wrote:
> Nathan wrote:
> > -	top_cpuset.cpus_allowed = cpu_online_map;
> > +	top_cpuset.cpus_allowed = cpu_possible_map;
> 
> NAQ
> 
> While this seems sensible on systems not using cpusets (but still using
> kernels configured for cpusets), it is surprising on systems using
> cpusets, on which one expects the cpuset that a task is in to reflect
> the cpus that a task is allowed to use.

Will it actually break anything?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/