numactl using it's own affinity to determine CPU set

If you set the affinity of your shell to be a subset of the available
CPUs, and then attempt to use numactl to bind to something that is not
in that affinity mask, the attempt will fail. I thought that this was
fixed in the current numactl 2.0.8, but it doesn't seem to be.

A simple reproducer on a 2-node 8-core system is as such:

$ numactl --physcpubind=5 ls
<see directory goodness>
$ taskset -p f $$
$ numactl --physcpubind=5 ls
libnuma: Warning: cpu argument 5 is out of range
<snip>

Let me know if more info is required.