From: Peter Zijlstra <peterz@infradead.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Josh Poimboeuf <jpoimboe@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Suren Baghdasaryan <surenb@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: avoid false-positive objtool warning in page_fault_oops()
Date: Tue, 17 Dec 2024 12:47:56 +0100 [thread overview]
Message-ID: <20241217114756.GE11133@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241217083059.1124426-1-arnd@kernel.org>
On Tue, Dec 17, 2024 at 09:30:41AM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> When printing the oops for a VMAP_STACK overflow, the final call
> frompage_fault_oops() does not return to the original stack, which
> confuses gcc, and the unreachable() annotation leads to the end
> of the function just continuing on in the next one:
>
> arch/x86/mm/fault.o: warning: objtool: page_fault_oops() falls through to next function kernelmode_fixup_or_oops.constprop.0()
>
> To work around the warning, add an explicit endless loop here that
> objtool can detect.
>
> Fixes: 6271cfdfc0e4 ("x86/mm: Improve stack-overflow #PF handling")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> I'm not sure about this one, maybe there is a way for objtool to
> detect this and not warn?
> ---
> arch/x86/mm/fault.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
> index e6c469b323cc..0ef6e3cc54d2 100644
> --- a/arch/x86/mm/fault.c
> +++ b/arch/x86/mm/fault.c
> @@ -678,7 +678,7 @@ page_fault_oops(struct pt_regs *regs, unsigned long error_code,
> ASM_CALL_ARG3,
> , [arg1] "r" (regs), [arg2] "r" (address), [arg3] "r" (&info));
>
> - unreachable();
> + do { } while (1); /* unreachable */
Ah, I have one that puts a BUG() there, like 2190966fbc14 ("x86: Convert
unreachable() to BUG()").
For some reason this hunk went missing from that patch.
prev parent reply other threads:[~2024-12-17 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:30 [PATCH] x86/mm: avoid false-positive objtool warning in page_fault_oops() Arnd Bergmann
2024-12-17 11:47 ` Peter Zijlstra [this message]
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=20241217114756.GE11133@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--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