seccomp: fix inverted notify socket setup logic

[caxu-rh]

In 3a8c913, the conditional in src/conmon.c was inadvertently reversed when the syntax was changed.

3a8c913#diff-737dc81597d3e3189077545b4907aae69cce646d12b5bc5938cfdd707882bd31R181

diff --git a/src/conmon.c b/src/conmon.c
index 795701c68f754cee5d22422e12872ca24748472a..7dd1f0b560c0e593dc289f42e35931554dcb7fd9 100644
--- a/src/conmon.c
+++ b/src/conmon.c
@@ -178,7 +178,7 @@ int main(int argc, char *argv[])
 	}
 
 	if (opt_seccomp_notify_socket != NULL) {
-#if !USE_SECCOMP
+#ifdef USE_SECCOMP
 		pexit("seccomp support not present");
 #else
 		if (opt_seccomp_notify_plugins == NULL)

[kolyshkin]

LGTM

[jnovy]

@kolyshkin re-enabling the seccomp logic (which is broken and never used in conmon) introduces a lot of regressions. @giuseppe FYI - assuming we should keep this disabled?

[giuseppe]

Yes, we haven't yet found a way to deal with seccomp notifications in conmon

[kolyshkin]

@kolyshkin re-enabling the seccomp logic (which is broken and never used in conmon) introduces a lot of regressions.

Are you saying this patch should be reverted? Or that we should never enable seccomp notifications (perhaps by removing the code entirely)?