Re: numactl problems with -C option specifying cpus outside of cpus_allowed

Christoph Lameter <[email protected]> Thu, 3 Oct 2013 17:37:24 +0000
Newsgroups org.kernel.vger.linux-numa
Message-ID <000001417f654322-16016bf3-6c9e-4a9c-a1c9-8426bb84d854-000000@email.amazonses.com>
On Thu, 3 Oct 2013, Petr Holasek wrote:

> On Thu, 03 Oct 2013, Christoph Lameter wrote:
> > On Wed, 2 Oct 2013, Andi Kleen wrote:
> >
> > > On Wed, Oct 02, 2013 at 02:34:01PM +0000, Christoph Lameter wrote:
> > > > It seems that the check for processors specified with C is always done
> > > > regardless of CAP_SYS_NICE or the possibility that root may be calling
> > > > numactl.
> > > >
> > > > taskset does not have that problem. Nor did releases of numactl before
> > > > 2.0.8.
> > >
> > > The recently added --all option may help?
> >
> > Which version added --all? Would the correct approach not be to check if
> > its root runninng numactl or if CAP_SYS_NICE is set?
>
> --all option was added in version 2.0.9-rc5. When CAP_SYS_NICE is not set,
> numactl will fail in sched_setaffinity() call even so.

numactl should allow the setting of affinities if CAP_SYS_NICE is set.