tests: rely on __SNR_xxx instead of __NR_xxx for syscalls
authorPaul Moore <paul@paul-moore.com>
Tue, 5 Nov 2019 20:11:11 +0000 (15:11 -0500)
committerFelix Geyer <fgeyer@debian.org>
Fri, 15 Nov 2019 17:12:53 +0000 (17:12 +0000)
commitafa79a8221ac2acc3c620c2fe0f77980e1a6e910
tree1e7fa15e77930f4cc4ee542cc9a1c32b35e4c60c
parent8936fee476196efe163e9804219ba22c049e1b32
tests: rely on __SNR_xxx instead of __NR_xxx for syscalls

We recently changed how libseccomp handles syscall numbers that are
not defined natively, but we missed test #15.

Signed-off-by: Paul Moore <paul@paul-moore.com>
Note: Tagged for v2.5, but needed to build 2.4.2 with newer kernels on arm
This is part of PR: https://github.com/seccomp/libseccomp/pull/182
Upstream Bug: https://github.com/seccomp/libseccomp/issues/184
Origin: upstream, https://github.com/pcmoore/misc-libseccomp/commit/35803ceb43c453762a3ab5177c5f8d5dbb813478
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1849785
Last-Update: 2019-11-12

Gbp-Pq: Name tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
tests/15-basic-resolver.c