lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aPnxlEkV1rL0hWOm@pathway.suse.cz>
Date: Thu, 23 Oct 2025 11:12:52 +0200
From: Petr Mladek <pmladek@...e.com>
To: Venkat Rao Bagalkote <venkat88@...ux.ibm.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
	linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Madhavan Srinivasan <maddy@...ux.ibm.com>,
	Hari Bathini <hbathini@...ux.ibm.com>, joe.lawrence@...hat.com,
	Naveen N Rao <naveen@...nel.org>,
	Masahiro Yamada <masahiroy@...nel.org>, jpoimboe@...nel.org
Subject: Re: [next-20251022] Kernel Boot Warnings at
 arch/powerpc/kernel/trace/ftrace.c:234

On Wed 2025-10-22 19:56:45, Venkat Rao Bagalkote wrote:
> 
> On 22/10/25 6:36 pm, Petr Mladek wrote:
> > On Wed 2025-10-22 17:36:18, Venkat Rao Bagalkote wrote:
> > > On 22/10/25 1:52 pm, Venkat Rao Bagalkote wrote:
> > > > Greetings!!!
> > > > 
> > > > 
> > > > IBM CI has reported kernel boot warnings with next-20251022 kernel. I
> > > > see there are couple of warnings hit and eventually system boots to
> > > > emergency mode.
> > > > 
> > > > 
> > > With the identified first bad commit, is casuing the kernel to boot to
> > > emergency mode. I reverted the bad commit and built the kernel, then kernel
> > > is booting fine, but with boot warnings.
> > I guess that it is the same problem which should get fixed by the patch
> > https://lore.kernel.org/r/e52ee3edf32874da645a9e037a7d77c69893a22a.1760982784.git.jpoimboe@kernel.org
> 
> 
> Thank you Petr, for pointing to the fix patch. It fixes the kernel booting
> to emergency mode.

Great.

> But boot warning still persists.

I looks like another problem. I would expect that it is in
the ftrace code, either in the generic or arch-specific part.

I would suggest to add people proposed by:

$> ./scripts/get_maintainer.pl arch/powerpc/kernel/trace/ftrace.c
Steven Rostedt <rostedt@...dmis.org> (maintainer:FUNCTION HOOKS (FTRACE))
Masami Hiramatsu <mhiramat@...nel.org> (maintainer:FUNCTION HOOKS (FTRACE))
Mark Rutland <mark.rutland@....com> (reviewer:FUNCTION HOOKS (FTRACE))
Madhavan Srinivasan <maddy@...ux.ibm.com> (maintainer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Michael Ellerman <mpe@...erman.id.au> (maintainer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Nicholas Piggin <npiggin@...il.com> (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
Christophe Leroy <christophe.leroy@...roup.eu> (reviewer:LINUX FOR POWERPC (32-BIT AND 64-BIT))
linux-kernel@...r.kernel.org (open list:FUNCTION HOOKS (FTRACE))
linux-trace-kernel@...r.kernel.org (open list:FUNCTION HOOKS (FTRACE))
linuxppc-dev@...ts.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND 64-BIT))
LINUX FOR POWERPC (32-BIT AND 64-BIT) status: Supported

into the original message with the backtrace. Or maybe, send it
once again and mention just the WARNING. The boot to the emergency
mode has been already solved...

Best Regards,
Petr

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ