From: sashiko-bot@kernel.org
To: "Ricardo Robaina" <rrobaina@redhat.com>
Cc: audit@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v3 05/14] microblaze: pass pt_regs to audit_syscall_entry()
Date: Tue, 22 Sep 2026 19:30:32 +0000 [thread overview]
Message-ID: <20260922193032.76CBD1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <8bf782579aa4e549f201e67856600b4a3445ad66.1790088067.git.rrobaina@redhat.com>
> audit_syscall_entry() now takes a pointer to pt_regs and extracts
> the syscall arguments itself via syscall_get_arguments(). Drop the
> individual argument registers from the call and pass regs instead.
>
> Signed-off-by: Ricardo Robaina <rrobaina@redhat.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790088067.git.rrobaina@redhat.com?part=5
next prev parent reply other threads:[~2026-09-22 19:30 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 [this message]
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
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=20260922193032.76CBD1F000FF@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