https://bugs.kde.org/show_bug.cgi?id=345414
--- Comment #23 from Miroslav Franc <mfr...@gmx.com> --- Created attachment 175865 --> https://bugs.kde.org/attachment.cgi?id=175865&action=edit seccomp syscall: warn only once I was also thinking about reducing the amount of warnings for the bad case. One option would be not to warn, and another to warn only once. Perhaps, it could be hidden behind a macro instead of the repetition, but I'm not sure. The trouble is that libseccomp is misusing seccomp api to check whether seccomp is supported at all on older kernels by invoking the syscall with an invalid combination of arguments and looking at the error code and this is happening more than once. > $ valgrind /usr/bin/file /etc/passwd > ==219469== Memcheck, a memory error detector > ==219469== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. > ==219469== Using Valgrind-3.25.0.GIT and LibVEX; rerun with -h for copyright > info > ==219469== Command: /usr/bin/file /etc/passwd > ==219469== > ==219469== WARNING: in STRICT SECCOMP mode 2nd argument (flags) should always > be 0 > ==219469== WARNING: valgrind is unlikely to work in STRICT SECCOMP mode > ==219469== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point > to struct sock_fprog > ==219469== WARNING: valgrind might not work in FILTER SECCOMP mode > Bad system call -- You are receiving this mail because: You are watching all bug changes.
