From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Thomas Gleixner <tglx@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux-kernel@vger.kernel.org,
Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: [PATCH 1/2] entry: Fix return type of syscall_trace_enter()
Date: Fri, 30 Oct 2026 13:31:41 +0100 [thread overview]
Message-ID: <20261030-wip-flo-fixup-entry-code-v1-1-7724c29e800b@siemens.com> (raw)
In-Reply-To: <20261030-wip-flo-fixup-entry-code-v1-0-7724c29e800b@siemens.com>
All return values of syscall_trace_enter() were migrated to bool in
commit 71ff30013f19 ("entry: Make return type of syscall_trace_enter() bool"),
but the function declaration has not been updated.
Fixing that up now.
Fixes: 71ff30013f19 ("entry: Make return type of syscall_trace_enter() bool")
Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
include/linux/entry-common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/entry-common.h b/include/linux/entry-common.h
index fa2854fed1f289b9d2dffbc4bf70ab9927f36917..a8b2430eadc5f8500195454e24f86cd9e0d06614 100644
--- a/include/linux/entry-common.h
+++ b/include/linux/entry-common.h
@@ -62,7 +62,7 @@ void trace_syscall_enter(struct pt_regs *regs);
void trace_syscall_exit(struct pt_regs *regs, long ret);
void syscall_enter_audit(struct pt_regs *regs);
-static __always_inline long syscall_trace_enter(struct pt_regs *regs, unsigned long work,
+static __always_inline bool syscall_trace_enter(struct pt_regs *regs, unsigned long work,
long syscall)
{
/*
--
2.56.0
next prev parent reply other threads:[~2026-10-30 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 12:31 [PATCH 0/2] entry: Drive-by fixes for the entry code Florian Bezdeka
2026-10-30 12:31 ` Florian Bezdeka [this message]
2026-10-30 12:31 ` [PATCH 2/2] entry: Complete syscall_enter_from_user_mode_work() to bool migration Florian Bezdeka
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=20261030-wip-flo-fixup-entry-code-v1-1-7724c29e800b@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=tglx@kernel.org \
/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®