From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sean Christopherson <seanjc@google.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
KP Singh <kpsingh@kernel.org>, Waiman Long <longman@redhat.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH v5 1/3] x86/syscall: Mark exit[_group] syscall handlers __noreturn
Date: Tue, 25 Jun 2024 22:21:17 -0700 [thread overview]
Message-ID: <20240626052117.tej46l7koshgk3hb@treble> (raw)
In-Reply-To: <b77e5491-77ec-4a4f-8ea9-4842b6923bfa@suse.com>
On Mon, May 27, 2024 at 02:15:57PM +0300, Nikolay Borisov wrote:
>
>
> On 7.05.24 г. 8:30 ч., Josh Poimboeuf wrote:
> > The direct-call syscall dispatch function doesn't know that the exit()
> > and exit_group() syscall handlers don't return, so the call sites aren't
> > optimized accordingly.
> >
> > Fix that by marking those exit syscall declarations __noreturn.
> >
> > Fixes the following warnings:
> >
> > vmlinux.o: warning: objtool: x64_sys_call+0x2804: __x64_sys_exit() is missing a __noreturn annotation
> > vmlinux.o: warning: objtool: ia32_sys_call+0x29b6: __ia32_sys_exit_group() is missing a __noreturn annotation
> >
> > Fixes: 7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall entry")
> > Reported-by: "Paul E. McKenney" <paulmck@kernel.org>
> > Closes: https://lkml.kernel.org/lkml/6dba9b32-db2c-4e6d-9500-7a08852f17a3@paulmck-laptop
> > Tested-by: Paul E. McKenney <paulmck@kernel.org>
> > Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
> > ---
> > arch/x86/entry/syscall_32.c | 10 ++++++----
> > arch/x86/entry/syscall_64.c | 9 ++++++---
> > arch/x86/entry/syscall_x32.c | 7 +++++--
> > arch/x86/entry/syscalls/syscall_32.tbl | 6 +++---
> > arch/x86/entry/syscalls/syscall_64.tbl | 6 +++---
> > arch/x86/um/sys_call_table_32.c | 10 ++++++----
> > arch/x86/um/sys_call_table_64.c | 11 +++++++----
> > scripts/syscalltbl.sh | 18 ++++++++++++++++--
> > tools/objtool/noreturns.h | 4 ++++
> > 9 files changed, 56 insertions(+), 25 deletions(-)
> >
> > diff --git a/arch/x86/entry/syscall_32.c b/arch/x86/entry/syscall_32.c
> > index c2235bae17ef..8cc9950d7104 100644
> > --- a/arch/x86/entry/syscall_32.c
> > +++ b/arch/x86/entry/syscall_32.c
> > @@ -14,9 +14,12 @@
> > #endif
> > #define __SYSCALL(nr, sym) extern long __ia32_##sym(const struct pt_regs *);
> > -
> > +#define __SYSCALL_NORETURN(nr, sym) extern long __noreturn __ia32_##sym(const struct pt_regs *);
> > #include <asm/syscalls_32.h>
> > -#undef __SYSCALL
> > +#undef __SYSCALL
> > +
> > +#undef __SYSCALL_NORETURN
> > +#define __SYSCALL_NORETURN __SYSCALL
> > /*
> > * The sys_call_table[] is no longer used for system calls, but
> > @@ -28,11 +31,10 @@
> > const sys_call_ptr_t sys_call_table[] = {
> > #include <asm/syscalls_32.h>
> > };
> > -#undef __SYSCALL
> > +#undef __SYSCALL
>
> nit: Am I blind or all the __SYSCALL lines have an extra whitespace?
>
> <snip>
That was a small readability tweak to make '__SYSCALL' vertically aligned:
#define __SYSCALL(nr, sym) extern long __ia32_##sym(const struct pt_regs *);
#define __SYSCALL_NORETURN(nr, sym) extern long __noreturn __ia32_##sym(const struct pt_regs *);
#include <asm/syscalls_32.h>
#undef __SYSCALL
--
Josh
next prev parent reply other threads:[~2024-06-26 5:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 5:30 [PATCH v5 0/3] x86/bugs: more BHI Josh Poimboeuf
2024-05-07 5:30 ` [PATCH v5 1/3] x86/syscall: Mark exit[_group] syscall handlers __noreturn Josh Poimboeuf
2024-05-07 14:38 ` Paul E. McKenney
2024-06-26 2:21 ` Paul E. McKenney
2024-06-26 5:28 ` Josh Poimboeuf
2024-06-26 6:35 ` Paul E. McKenney
2024-06-27 6:36 ` Alexandre Chartre
2024-05-27 11:15 ` Nikolay Borisov
2024-06-26 5:21 ` Josh Poimboeuf [this message]
2024-05-07 5:30 ` [PATCH v5 2/3] x86/bugs: Remove duplicate Spectre cmdline option descriptions Josh Poimboeuf
2024-05-07 15:04 ` Daniel Sneddon
2024-05-08 5:55 ` Josh Poimboeuf
2024-05-08 14:28 ` Daniel Sneddon
2024-05-07 5:30 ` [PATCH v5 3/3] x86/bugs: Add 'spectre_bhi=vmexit' cmdline option Josh Poimboeuf
2024-05-07 14:58 ` Daniel Sneddon
2024-05-08 5:19 ` Josh Poimboeuf
2024-05-27 10:45 ` Maksim Davydov
2024-06-26 5:58 ` Josh Poimboeuf
2024-05-08 15:10 ` Nikolay Borisov
2024-05-09 5:24 ` Josh Poimboeuf
2024-05-09 8:21 ` Nikolay Borisov
2024-05-20 13:12 ` Maksim Davydov
2024-05-23 1:04 ` Josh Poimboeuf
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=20240626052117.tej46l7koshgk3hb@treble \
--to=jpoimboe@kernel.org \
--cc=alexandre.chartre@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=nik.borisov@suse.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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®