From: sashiko-bot@kernel.org
To: "Mete Durlu" <meted@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>
Subject: Re: [PATCH 2/3] s390: Implement arch_do_panic
Date: Mon, 27 Jul 2026 09:10:40 +0000 [thread overview]
Message-ID: <20260727091040.A7F791F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727-arch_do_panic-v1-2-ca1777547c38@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] arch_do_panic() is bypassed when panic_timeout != 0
- [Low] Unused declaration of s390_do_panic()
--
--- Patch [2]: [PATCH 2/3] s390: Implement arch_do_panic ---
commit 640e72aef0a165dacc87c9e5913aa8f9442aa6e9
Author: Mete Durlu <meted@linux.ibm.com>
s390: Implement arch_do_panic
This commit implements the arch_do_panic() hook for s390 to handle
architecture-specific panic actions instead of relying on the panic_notifier
chain. This change allows user-specified panic_timeout values to be evaluated
in common code before executing the s390 specific actions.
> diff --git a/arch/s390/include/asm/ipl.h b/arch/s390/include/asm/ipl.h
> index b0d00032479d6..38924c4a5d1d7 100644
> --- a/arch/s390/include/asm/ipl.h
> +++ b/arch/s390/include/asm/ipl.h
> @@ -166,5 +166,6 @@ enum diag308_rc {
> extern int diag308(unsigned long subcode, void *addr);
> extern void store_status(void (*fn)(void *), void *data);
> extern void lgr_info_log(void);
> +void s390_do_panic(void);
[Severity: Low]
Is this declaration necessary?
It looks like s390_do_panic() is declared here but never implemented or used,
as the actual implementation provided in arch/s390/kernel/ipl.c is named
arch_do_panic().
[ ... ]
> diff --git a/kernel/panic.c b/kernel/panic.c
> index 1eb0cdc159d94..de0bda946cabb 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -755,9 +755,6 @@ void vpanic(const char *fmt, va_list args)
> pr_emerg("Press Stop-A (L1-A) from sun keyboard or send break\n"
> "twice on console to return to the boot prom\n");
> }
> -#endif
> -#if defined(CONFIG_S390)
> - disabled_wait();
> #endif
> pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
[Severity: High]
Does this change unintentionally bypass the s390 panic actions when
panic_timeout != 0?
Looking at vpanic() in kernel/panic.c, if a panic timeout is set, the system
will restart before reaching arch_do_panic():
if (panic_timeout != 0) {
...
emergency_restart();
}
pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
arch_do_panic();
Since emergency_restart() does not return, will the user-configured on_panic
actions be lost in this scenario?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-arch_do_panic-v1-0-ca1777547c38@linux.ibm.com?part=2
next prev parent reply other threads:[~2026-07-27 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 8:58 [PATCH 0/3] Introduce arch_do_panic Mete Durlu
2026-07-27 8:58 ` [PATCH 1/3] panic: " Mete Durlu
2026-07-27 9:09 ` sashiko-bot
2026-07-27 8:58 ` [PATCH 2/3] s390: Implement arch_do_panic Mete Durlu
2026-07-27 9:10 ` sashiko-bot [this message]
2026-07-27 9:35 ` Mete Durlu
2026-07-27 8:58 ` [PATCH 3/3] sparc: " Mete Durlu
2026-07-27 9:11 ` sashiko-bot
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=20260727091040.A7F791F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.