237
90%
main: 89%

Ran 01 Oct 2019 06:45AM UTC

Jobs 1

Files 59

Run time 4s

Badge

Embed ▾

pending completion

Build # 237

Build Type

Pull #172

travis-ci

Committed by

web-flow

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.

Signed-off-by: Paul Moore <paul@paul-moore.com>

Pull Request Pull Request #172: api: stop defining __NR_x values for syscalls that don't exist

Run Details

2349 of 2616 relevant lines covered (89.79%)

3002783.04 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	237.1	01 Oct 2019 06:45AM UTC	0	89.79	Travis Job 237.1

Source Files on build 237

Detailed source file information is not available for this build.

seccomp / libseccomp / 237
90%
main: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 237

seccomp / libseccomp / 237 90% main: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 237

seccomp / libseccomp / 237
90%
main: 89%

README BADGES
x