Comment 5 for bug 1821625

I'm leaving this as marked against libseccomp, as I don't understand why it is redefining kernel header values as invalid numbers in its public header file (so that other programs using its header files pull in those invalid syscall numbers). I don't think it should but I'll leave the decision to discuss this upstream to someone more familiar with libseccomp.