From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Yunhui Cui" <cuiyunhui@bytedance.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: use KERN_INFO in do_trap
Date: Tue, 13 Feb 2024 10:59:58 +0100 [thread overview]
Message-ID: <mvmh6ic1y75.fsf@suse.de> (raw)
Print the instruction dump with info instead of emergency level like the
rest of the output when printing the information for an unhandled signal.
Fixes: b8a03a634129 ("riscv: add userland instruction dump to RISC-V splats")
Signed-off-by: Andreas Schwab <schwab@suse.de>
---
arch/riscv/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/kernel/traps.c b/arch/riscv/kernel/traps.c
index a1b9be3c4332..142f5f5168fb 100644
--- a/arch/riscv/kernel/traps.c
+++ b/arch/riscv/kernel/traps.c
@@ -121,7 +121,7 @@ void do_trap(struct pt_regs *regs, int signo, int code, unsigned long addr)
print_vma_addr(KERN_CONT " in ", instruction_pointer(regs));
pr_cont("\n");
__show_regs(regs);
- dump_instr(KERN_EMERG, regs);
+ dump_instr(KERN_INFO, regs);
}
force_sig_fault(signo, code, (void __user *)addr);
--
2.43.1
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Yunhui Cui" <cuiyunhui@bytedance.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: use KERN_INFO in do_trap
Date: Tue, 13 Feb 2024 10:59:58 +0100 [thread overview]
Message-ID: <mvmh6ic1y75.fsf@suse.de> (raw)
Print the instruction dump with info instead of emergency level like the
rest of the output when printing the information for an unhandled signal.
Fixes: b8a03a634129 ("riscv: add userland instruction dump to RISC-V splats")
Signed-off-by: Andreas Schwab <schwab@suse.de>
---
arch/riscv/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/kernel/traps.c b/arch/riscv/kernel/traps.c
index a1b9be3c4332..142f5f5168fb 100644
--- a/arch/riscv/kernel/traps.c
+++ b/arch/riscv/kernel/traps.c
@@ -121,7 +121,7 @@ void do_trap(struct pt_regs *regs, int signo, int code, unsigned long addr)
print_vma_addr(KERN_CONT " in ", instruction_pointer(regs));
pr_cont("\n");
__show_regs(regs);
- dump_instr(KERN_EMERG, regs);
+ dump_instr(KERN_INFO, regs);
}
force_sig_fault(signo, code, (void __user *)addr);
--
2.43.1
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next reply other threads:[~2024-02-13 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 9:59 Andreas Schwab [this message]
2024-02-13 9:59 ` [PATCH] riscv: use KERN_INFO in do_trap Andreas Schwab
2024-02-14 9:19 ` Conor Dooley
2024-02-14 9:19 ` Conor Dooley
2024-02-14 10:10 ` Andreas Schwab
2024-02-14 10:10 ` Andreas Schwab
2024-02-14 10:34 ` Conor Dooley
2024-02-14 10:34 ` Conor Dooley
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=mvmh6ic1y75.fsf@suse.de \
--to=schwab@suse.de \
--cc=bjorn@rivosinc.com \
--cc=cuiyunhui@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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 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.