From: Jeffrey Bencteux <jeff@bencteux.fr>
To: paul@paul-moore.com, eparis@redhat.com, arnd@arndb.de,
audit@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
jeff@bencteux.fr
Subject: [PATCH] audit: add missing syscalls to signal class
Date: Wed, 11 Nov 2026 12:01:54 +0100 [thread overview]
Message-ID: <20261111110200.30415-1-jeff@bencteux.fr> (raw)
The pidfd_send_signal(), rt_sigqueueinfo() and rt_tgsigqueueinfo()
system calls are missing from the AUDIT_CLASS_SIGNAL* class. It seems
to be used only in kernel/auditfilter.c to increment the audit_signals
counter.
This counter is used to determine if information related to a target
process of a syscall audit rule using signals, such as its pid,
should be logged (e54dc2431d740a79a6bd013babade99d71b1714f).
Information related to signals sent via these system calls are
currently not correctly logged. The current patch adds it to the
AUDIT_CLASS_SIGNAL* class.
Signed-off-by: Jeffrey Bencteux <jeff@bencteux.fr>
---
include/asm-generic/audit_signal.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/asm-generic/audit_signal.h b/include/asm-generic/audit_signal.h
index 6feab7f18a53..65336a9aef7b 100644
--- a/include/asm-generic/audit_signal.h
+++ b/include/asm-generic/audit_signal.h
@@ -1,3 +1,12 @@
__NR_kill,
__NR_tgkill,
__NR_tkill,
+#ifdef __NR_rt_sigqueueinfo
+__NR_rt_sigqueueinfo,
+#endif
+#ifdef __NR_rt_tgsigqueueinfo
+__NR_rt_tgsigqueueinfo,
+#endif
+#ifdef __NR_pidfd_send_signal
+__NR_pidfd_send_signal,
+#endif
base-commit: 6614d4c05c7a661a925b3d8dbf9c70faac3bd2da
--
2.56.0
next reply other threads:[~2026-11-11 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:01 Jeffrey Bencteux [this message]
2026-11-11 11:18 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261111110200.30415-1-jeff@bencteux.fr \
--to=jeff@bencteux.fr \
--cc=arnd@arndb.de \
--cc=audit@vger.kernel.org \
--cc=eparis@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®