All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] core/urgent fixes
Date: Sun, 15 Nov 2026 13:02:51 +0100	[thread overview]
Message-ID: <avmfa9udOnu4gFmp@gmail.com> (raw)

Linus,

Please pull the latest core/urgent Git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-2026-11-15

for you to fetch changes up to efe191f1605a149b06eb0fe1ff975e7d3137c9bb:

 - Two generic syscall entry code fixes for return code
   data type definitions. (Florian Bezdeka)

 Thanks,

	Ingo

------------------>
Florian Bezdeka (2):
      entry: Fix return type of syscall_trace_enter()
      entry: Complete syscall_enter_from_user_mode_work() to bool migration


 include/linux/entry-common.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/entry-common.h b/include/linux/entry-common.h
index fa2854fed1f2..15278416f886 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)
 {
 	/*
@@ -202,7 +202,7 @@ do {									\
 									\
 	instrumentation_begin();					\
 	local_irq_enable();						\
-	long _ret = syscall_enter_from_user_mode_work(regs, syscall);	\
+	bool _ret = syscall_enter_from_user_mode_work(regs, syscall);	\
 	instrumentation_end();						\
 									\
 	_ret;								\

             reply	other threads:[~2026-11-15 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 12:02 Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-23 16:45 [GIT PULL] core/urgent fixes Ingo Molnar
2026-06-24  0:20 ` pr-tracker-bot
2026-04-20  7:37 Ingo Molnar
2026-04-20 23:31 ` pr-tracker-bot
2025-12-12  9:30 Ingo Molnar
2025-12-13 18:12 ` pr-tracker-bot
2025-04-18 20:18 Ingo Molnar
2025-04-18 20:28 ` pr-tracker-bot
2019-04-12 10:16 Ingo Molnar
2019-04-13  4:05 ` pr-tracker-bot
2017-03-07 20:18 Ingo Molnar
2014-10-31 10:21 Ingo Molnar

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=avmfa9udOnu4gFmp@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.