api: don't allow the TSYNC and NEW_LISTENER flags at the same time
api: don't allow the TSYNC and NEW_LISTENER flags at the same time

Because TSYNC and NEW_LISTENER send information back via the
seccomp(...) return value, they can not be used at the same time. It
seems like the right thing to do is to always set the NEW_LISTENER
flag (as long as the API level supports it) unless the caller
explicitly sets TSYNC.

Acked-by: Tom Hromatka <96b9c1f2c09b98d7a09b4688fc637f1494d8e182@oracle.com>
Signed-off-by: Paul Moore <a027184a55211cd23e3f3094f1fdc728df5e0500@paul-moore.com>

seccomp/libseccomp,seccomp/libseccomp,seccomp/libseccomp