From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Gabriele Monaco <gmonaco@redhat.com>,
Nam Cao <namcao@linutronix.de>, John Kacur <jkacur@redhat.com>,
Tomas Glozar <tglozar@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] runtime verification: Updates for 6.17
Date: Sat, 16 Aug 2025 14:43:54 +0100 [thread overview]
Message-ID: <aKCLGvmPLPwjyw13@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAFLxGvxZJv_A+YKCxVcd4yxPXLhHD5L9VzkvbFKPytxXc5vWaw@mail.gmail.com>
On Sat, Aug 16, 2025 at 02:04:34PM +0200, Richard Weinberger wrote:
> [Adding ARM folks]
>
> On Tue, Jul 29, 2025 at 11:43 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> > Linus,
> >
> > Runtime verification changes for 6.17
>
> [...]
>
> > - Add a vpanic() to allow for va_list to be passed to panic.
>
> This change is causing a regression on ARM32.
> panic() no longer shows a proper stack trace.
>
> With this change:
> [ 2.943690] Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(0,0)
> [ 2.950101] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted
> 6.17.0-rc1 #176 NONE
> [ 2.950509] Hardware name: Generic DT based system
> [ 2.950865] Call trace:
> [ 2.951722] unwind_backtrace from show_stack+0x18/0x1c
> [ 2.953111] show_stack from dump_stack_lvl+0x54/0x68
> [ 2.953312] dump_stack_lvl from vpanic+0xf8/0x388
> [ 2.953526] vpanic from __do_trace_suspend_resume+0x0/0x50
Please lookup the value of __do_trace_suspend_resume in System.map.
>
> With commit 3f045de7f5 "panic: Add vpanic()" reverted:
> [ 2.680077] Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(0,0)
> [ 2.690241] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted
> 6.17.0-rc1-dirty #177 NONE
> [ 2.690832] Hardware name: Generic DT based system
> [ 2.691339] Call trace:
> [ 2.692530] unwind_backtrace from show_stack+0x18/0x1c
> [ 2.694283] show_stack from dump_stack_lvl+0x54/0x68
> [ 2.694536] dump_stack_lvl from panic+0x110/0x31c
> [ 2.694944] panic from mount_root_generic+0x1fc/0x2ac
Also please lookup mount_root_generic.
> Maybe it changes the stack layout enough such that dump_stack() on
> ARM32 is no longer
> able to walk it? I'm using gcc 15.1.1, if this matters.
Also please check whether you're using frame pointers or the unwinder
(CONFIG_UNWINDER_FRAME_POINTER or CONFIG_ARM_UNWIND).
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-08-16 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:43 [GIT PULL] runtime verification: Updates for 6.17 Steven Rostedt
2025-07-31 0:35 ` pr-tracker-bot
2025-08-16 12:04 ` Richard Weinberger
2025-08-16 12:08 ` Richard Weinberger
2025-08-16 13:43 ` Russell King (Oracle) [this message]
2025-08-16 19:26 ` Richard Weinberger
2025-08-18 8:41 ` Richard Weinberger
2025-09-02 20:51 ` Richard Weinberger
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=aKCLGvmPLPwjyw13@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=gmonaco@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=richard.weinberger@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
--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 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).