** Description changed: [ Impact ] numactl 2.0.18-1build1 has a bug, wherein trying to set a node for memory using membind emits an "Invalid argument" error. Ubuntu: 24.04.3 LTS (Noble Numbat) Kernel: 6.8.0-90.91 libnuma1: 2.0.18-1build1 numactl: 2.0.18-1build1 This bugfix should be backported since numactl crashes if MPOL_PREFERRED_MANY isn't supported. The fix is to not clobber errno, if the set_mempolicy syscall fails: https://github.com/numactl/numactl/commit/6c14bd59d438ebb5ef828e393e8563ba18f59cb2 More details of this issue can be found here: https://github.com/numactl/numactl/issues/223 [ Test Plan ] - install numactl from 24.04 on machine without MPOL_PREFERRED_MANY - support - - $ numactl --membind=0 echo success - setting membind: Invalid argument - - with the fix, it should print "success". - + - Launch a Focal VM (kernel old enough to not support MPOL_PREFERRED_MANY) + - Inside of the VM, launch a Noble container + - install numactl from the archive + - run $ numactl --membind=0 echo success and see it fail with the error above + - install numactl from -proposed + - run $ numactl --membind=0 echo success and see 'success' [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the - change is wrong or breaks something else: how would this show up? + * Think about what the upload changes in the software. Imagine the + change is wrong or breaks something else: how would this show up? - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the event - of a regression. + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the event + of a regression. - * This must never be "None" or "Low", or entirely an argument as to why - your upload is low risk. + * This must never be "None" or "Low", or entirely an argument as to why + your upload is low risk. - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. [ Original Report ] numactl 2.0.19-1 fixes the bug, and has already been built for questing. I have tested it on noble and it works without issues. Can we bump up the version of `numactl` on noble too? - * Anything else you think is useful to include + * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams - and the Technical Board and address these questions in advance + * Anticipate questions from users, SRU, +1 maintenance, security teams + and the Technical Board and address these questions in advance
** Description changed: [ Impact ] numactl 2.0.18-1build1 has a bug, wherein trying to set a node for memory using membind emits an "Invalid argument" error. Ubuntu: 24.04.3 LTS (Noble Numbat) Kernel: 6.8.0-90.91 libnuma1: 2.0.18-1build1 numactl: 2.0.18-1build1 This bugfix should be backported since numactl crashes if MPOL_PREFERRED_MANY isn't supported. The fix is to not clobber errno, if the set_mempolicy syscall fails: https://github.com/numactl/numactl/commit/6c14bd59d438ebb5ef828e393e8563ba18f59cb2 More details of this issue can be found here: https://github.com/numactl/numactl/issues/223 [ Test Plan ] - Launch a Focal VM (kernel old enough to not support MPOL_PREFERRED_MANY) - Inside of the VM, launch a Noble container - install numactl from the archive - run $ numactl --membind=0 echo success and see it fail with the error above - install numactl from -proposed - run $ numactl --membind=0 echo success and see 'success' [ Where problems could occur ] * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must never be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [ Original Report ] numactl 2.0.19-1 fixes the bug, and has already been built for questing. I have tested it on noble and it works without issues. Can we bump up the version of `numactl` on noble too? - - * Anything else you think is useful to include - - * Anticipate questions from users, SRU, +1 maintenance, security teams - and the Technical Board and address these questions in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2136104 Title: numactl gives "Invalid argument" error when trying to set a node for memory using membind To manage notifications about this bug go to: https://bugs.launchpad.net/appmajix/+bug/2136104/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
