From: Khalid Ali <khaliidcaliy@gmail.com>
To: tglx@linutronix.de, peterz@infradead.org, luto@kernel.org
Cc: linux-kernel@vger.kernel.org, Khalid Ali <khaliidcaliy@gmail.com>
Subject: [PATCH v2] entry: Use syscall work for auditing in
Date: Mon, 23 Jun 2025 07:00:30 +0000 [thread overview]
Message-ID: <20250623070136.662-1-khaliidcaliy@gmail.com> (raw)
Use SYSCALL_WORK_SYSCALL_AUDIT to check if audit needs to be done
instead of audit context for consistency to other syscall work bit
checks.
While audit_syscall_entry() also checks the audit context, this patch
replaces the upper audit context check (i.e in syscall_enter_audit())
from using audit context to syscall work.
This makes consistent with other syscall works. It also determines the
auditing should be done earlier before syscall_enter_audit() called.
As privious versions of this patch discussed, using syscall work is
cheaper and more cleaner than checking audit context in terms of
readability.
Signed-off-by: Khalid Ali <khaliidcaliy@gmail.com>
---
kernel/entry/common.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/kernel/entry/common.c b/kernel/entry/common.c
index f49e3440204d..3e9f2d40230f 100644
--- a/kernel/entry/common.c
+++ b/kernel/entry/common.c
@@ -17,12 +17,10 @@
static inline void syscall_enter_audit(struct pt_regs *regs, long syscall)
{
- if (unlikely(audit_context())) {
- unsigned long args[6];
+ unsigned long args[6];
- syscall_get_arguments(current, regs, args);
- audit_syscall_entry(syscall, args[0], args[1], args[2], args[3]);
- }
+ syscall_get_arguments(current, regs, args);
+ audit_syscall_entry(syscall, args[0], args[1], args[2], args[3]);
}
long syscall_trace_enter(struct pt_regs *regs, long syscall,
@@ -65,8 +63,9 @@ long syscall_trace_enter(struct pt_regs *regs, long syscall,
*/
syscall = syscall_get_nr(current, regs);
}
-
- syscall_enter_audit(regs, syscall);
+
+ if (unlikely(work & SYSCALL_WORK_SYSCALL_AUDIT))
+ syscall_enter_audit(regs, syscall);
return ret ? : syscall;
}
--
2.49.0
reply other threads:[~2025-06-23 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250623070136.662-1-khaliidcaliy@gmail.com \
--to=khaliidcaliy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).