239
93%
main: 89%

Ran 07 Oct 2019 11:35PM UTC

Jobs 1

Files 59

Run time 7s

Badge

Embed ▾

pending completion

Build # 239

Build Type

push

travis-ci

Committed by

pcmoore

Commit Message

api: stop defining __NR_x values for syscalls that don't exist

Historically libseccomp has created a __NR_x definition for every
syscall it supports, even those that aren't valid for a given ABI.
While this seemed like a good idea at the time, it turned out to have
some unwanted and nasty side effects.  This patch finally corrects
this problem.

The basic approach is quite simple: move the SCMP_SYS() macro to use
__SNR_x values instead of __NR_x values.  The unfortunate side effect
of this change is that instead of just worrying about #defines for the
__PNR_x values we now have to have a __SNR_x define for *every*
syscall.  The good news is that after this patch that should only be
a few new syscalls every year - a very manageable task.

Reviewed-by: Tom Hromatka <tom.hromatka@oracle.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>

Run Details

2349 of 2616 relevant lines covered (89.79%)

3002783.04 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	239.1	07 Oct 2019 11:35PM UTC	0	89.79	Travis Job 239.1

Source Files on build 239

Detailed source file information is not available for this build.

seccomp / libseccomp / 239
93%
main: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 239

seccomp / libseccomp / 239 93% main: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 239

seccomp / libseccomp / 239
93%
main: 89%

README BADGES
x