numad.8 | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix spelling mistakes on the manpage

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 do not override cflags
 Do not override CFLAGS so dpkg-buildflags works

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 install binaries on debian paths

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 do not remove debian dir
 upstream Makefile tries to remove too much

numad.init | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

---

numad.c | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 fix build for platforms with no __nr_migrate_pages syscall

numad.service | 5 2 + 3 - 0 !
1 file changed, 2 insertions(+), 3 deletions(-)

 numad doesn't read /etc/default/numad

numad.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 recognize -m option correctly

numad.c | 13 12 + 1 - 0 !
1 file changed, 12 insertions(+), 1 deletion(-)

 [patch] fix sparse node ids

CPU-ids can be sparse due to disabling a subset of CPUs.
On ppc64le this even will make the node_ids sparse, this is actually pretty
common on ppc64 when SMT is disabled.

Numad has the assumption of cpu/node-ids always being linear and due to that
accesses the 'node' array out of bounds. That triggers crashes like the
following:

  Thread 1 "numad" received signal SIGSEGV, Segmentation fault.
  #0 0x00000fb6cd2779f4 in bind_process_and_migrate_memory (p=0xfb6fc1e0f70)
    at numad.c:998
  #1 0x00000fb6cd27d148 in manage_loads () at numad.c:2225
  #2 0x00000fb6cd2734dc in main (argc=<optimized out>, argv=<optimized out>)
    at numad.c:2654

Instead of directly indexing with node_id we need to detect which array
element has the matching node_id and use that.