From: Shivang Upadhyay <shivangu@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, kees@kernel.org, tony.luck@intel.com,
gpiccoli@igalia.com, ritesh.list@gmail.com, rppt@kernel.org,
Shivang Upadhyay <shivangu@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Shirisha G <shirisha@linux.ibm.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>
Subject: [PATCH] ppc/fadump: invoke kmsg_dump in fadump panic path
Date: Tue, 7 Apr 2026 11:13:41 +0530 [thread overview]
Message-ID: <20260407054341.308710-1-shivangu@linux.ibm.com> (raw)
fadump is registered in panic_notifier_list and gets triggered
before kmsg_dump_desc() in the panic path. As a result,
kmsg_dumpers (e.g. pstore) are not executed.
Invoke kmsg_dump_desc() from the fadump handler to ensure
kmsg_dumpers are called during panic.
Cc: Hari Bathini <hbathini@linux.ibm.com>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
Reported-by: Shirisha G <shirisha@linux.ibm.com>
Suggested-by: Sourabh Jain <sourabhjain@linux.ibm.com>
Signed-off-by: Shivang Upadhyay <shivangu@linux.ibm.com>
---
arch/powerpc/kernel/setup-common.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index b1761909c23f..c329b071643d 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -68,6 +68,7 @@
#include <asm/kasan.h>
#include <asm/mce.h>
#include <asm/systemcfg.h>
+#include <linux/kmsg_dump.h>
#include "setup.h"
@@ -748,6 +749,8 @@ static int ppc_panic_fadump_handler(struct notifier_block *this,
* If firmware-assisted dump has been registered then trigger
* its callback and let the firmware handles everything else.
*/
+ kmsg_dump_desc(KMSG_DUMP_PANIC, (char *)ptr);
+
crash_fadump(NULL, ptr);
return NOTIFY_DONE;
--
2.53.0
next reply other threads:[~2026-04-07 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 5:43 Shivang Upadhyay [this message]
2026-04-07 15:30 ` [PATCH] ppc/fadump: invoke kmsg_dump in fadump panic path Sourabh Jain
2026-04-09 9:14 ` Shivang Upadhyay
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=20260407054341.308710-1-shivangu@linux.ibm.com \
--to=shivangu@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=hbathini@linux.ibm.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=shirisha@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=tony.luck@intel.com \
/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