From: sashiko-bot@kernel.org
To: "Ricardo Robaina" <rrobaina@redhat.com>
Cc: bpf@vger.kernel.org, audit@vger.kernel.org
Subject: Re: [PATCH v3 14/14] audit: rename audit_syscall_entry_regs() to audit_syscall_entry()
Date: Tue, 22 Sep 2026 19:37:52 +0000 [thread overview]
Message-ID: <20260922193753.087281F000FF@smtp.kernel.org> (raw)
In-Reply-To: <0bb32d256099870f3f9ca2632cccf58538f882ed.1790088067.git.rrobaina@redhat.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] build: alpha fails to compile due to unconverted audit_syscall_entry()
--
commit ec0fa766c1abca8ff2e93429fedc5d6b95059a19
Author: Ricardo Robaina <rrobaina@redhat.com>
audit: rename audit_syscall_entry_regs() to audit_syscall_entry()
Now that every architecture has been converted to the pt_regs-based
audit_syscall_entry_regs(), the legacy audit_syscall_entry() and
__audit_syscall_entry() helpers that took the individual syscall
argument registers (a0-a3) no longer have any callers.
Remove those legacy helpers and rename audit_syscall_entry_regs() and
__audit_syscall_entry_regs() back to audit_syscall_entry() and
__audit_syscall_entry(), restoring the original naming.
[ ... ]
> diff --git a/include/linux/audit.h b/include/linux/audit.h
> index 22ffad5b20608..9ce5962bc5370 100644
> --- a/include/linux/audit.h
> +++ b/include/linux/audit.h
> @@ -374,17 +372,10 @@ static inline void audit_uring_exit(int success, long code)
> if (unlikely(audit_context()))
> __audit_uring_exit(success, code);
> }
> -static inline void audit_syscall_entry(int major, unsigned long a0,
> - unsigned long a1, unsigned long a2,
> - unsigned long a3)
> +static inline void audit_syscall_entry(int major, struct pt_regs *regs)
> {
[Severity: Low]
The commit message states that every architecture has been converted, but does
this break the build for the Alpha architecture?
Looking at arch/alpha/kernel/ptrace.c:syscall_trace_enter(), there is still an
unconverted caller that passes 5 arguments to audit_syscall_entry():
arch/alpha/kernel/ptrace.c:syscall_trace_enter() {
...
#ifdef CONFIG_AUDITSYSCALL
audit_syscall_entry(syscall_get_nr(current, regs),
regs->r16, regs->r17, regs->r18, regs->r19);
#endif
...
}
Since the 5-argument helper has been removed and the renamed helper now
expects exactly 2 arguments, will this cause a 'too many arguments to
function' compilation error when building for Alpha?
> if (unlikely(audit_context()))
> - __audit_syscall_entry(major, a0, a1, a2, a3);
> -}
> -static inline void audit_syscall_entry_regs(int major, struct pt_regs *regs)
> -{
> - if (unlikely(audit_context()))
> - __audit_syscall_entry_regs(major, regs);
> + __audit_syscall_entry(major, regs);
> }
> static inline void audit_syscall_exit(void *pt_regs)
> {
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790088067.git.rrobaina@redhat.com?part=14
next prev parent reply other threads:[~2026-09-22 19:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:19 [PATCH v3 00/14] audit: log all six syscall arguments in the SYSCALL record Ricardo Robaina
2026-09-22 19:19 ` [PATCH v3 01/14] " Ricardo Robaina
2026-09-22 19:31 ` sashiko-bot
2026-09-23 11:29 ` Oleg Nesterov
2026-09-22 19:19 ` [PATCH v3 02/14] arm: pass pt_regs to audit_syscall_entry() Ricardo Robaina
2026-09-22 19:39 ` sashiko-bot
2026-09-22 19:19 ` [PATCH v3 03/14] arm64: " Ricardo Robaina
2026-09-22 19:31 ` sashiko-bot
2026-09-22 19:19 ` [PATCH v3 04/14] csky: " Ricardo Robaina
2026-09-22 19:32 ` sashiko-bot
2026-09-22 19:19 ` [PATCH v3 05/14] microblaze: " Ricardo Robaina
2026-09-22 19:30 ` sashiko-bot
2026-09-22 19:19 ` [PATCH v3 06/14] mips: " Ricardo Robaina
2026-09-22 19:33 ` sashiko-bot
2026-09-22 19:19 ` [PATCH v3 07/14] openrisc: " Ricardo Robaina
2026-09-22 19:33 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 08/14] parisc: mask compat syscall arguments in syscall_get_arguments() Ricardo Robaina
2026-09-22 19:33 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 09/14] parisc: pass pt_regs to audit_syscall_entry() Ricardo Robaina
2026-09-22 19:32 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 10/14] sh: " Ricardo Robaina
2026-09-22 19:33 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 11/14] sparc64: " Ricardo Robaina
2026-09-22 19:30 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 12/14] um: " Ricardo Robaina
2026-09-22 19:34 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 13/14] xtensa: " Ricardo Robaina
2026-09-22 19:36 ` sashiko-bot
2026-09-22 19:20 ` [PATCH v3 14/14] audit: rename audit_syscall_entry_regs() " Ricardo Robaina
2026-09-22 19:37 ` sashiko-bot [this message]
2026-09-23 11:30 ` Oleg Nesterov
2026-10-01 21:05 ` [PATCH v3 00/14] audit: log all six syscall arguments in the SYSCALL record Paul Moore
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=20260922193753.087281F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=audit@vger.kernel.org \
--cc=bpf@vger.kernel.org \
--cc=rrobaina@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
/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