What were you trying to do that didn't work?

numactl 2.18 introduced an upstream regression that breaks on kernels without MPOL_PREFERRED_MANY (e.g. 5.12). This was fixed upstream in https://github.com/numactl/numactl/commit/6c14bd59d438ebb5ef828e393e8563ba18f59cb2 which is part of 2.19. Please either rebase to 2.19 or cherrypick the fix. For reference, the Fedora package was updated to 2.19 for this (https://src.fedoraproject.org/rpms/numactl/c/7204d9c5c9422755aba122b41c2a22024f13caaa by jonathanspw).

What is the impact of this issue to you?

numactl --membind=0 fails, which in turn breaks an internal application that relies on it

Please provide the package NVR for which the bug is seen:

numactl-2.0.18-4.el10

numactl-2.0.18-3.el10

numactl-2.0.18-2.el10

How reproducible is this bug?:

always

Steps to reproduce

1. be running a kernel without MPOL_PREFERRED_MANY (e.g. 5.12)
2. numactl --membind=0 - ls
3. notice it fails

Expected results

The command should succeed

Actual results

1. numactl --membind=0 - ls

setting membind: Invalid argument