From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ryabinin.a.a@gmail.com,bp@alien8.de,akpm@linux-foundation.org
Subject: [merged mm-stable] ubsan-use-the-kernel-panic-message-markers.patch removed from -mm tree
Date: Wed, 20 Dec 2023 14:49:33 -0800 [thread overview]
Message-ID: <20231220224933.D37ACC433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: UBSAN: use the kernel panic message markers
has been removed from the -mm tree. Its filename was
ubsan-use-the-kernel-panic-message-markers.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Subject: UBSAN: use the kernel panic message markers
Date: Mon, 18 Dec 2023 14:53:39 +0100
Use the same splat markers as panic does for easier matching by external
tools scanning kernel dmesg for splats.
Link: https://lkml.kernel.org/r/20231218135339.23209-1-bp@alien8.de
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/ubsan.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--- a/lib/ubsan.c~ubsan-use-the-kernel-panic-message-markers
+++ a/lib/ubsan.c
@@ -204,8 +204,8 @@ static void ubsan_prologue(struct source
{
current->in_ubsan++;
- pr_err("========================================"
- "========================================\n");
+ pr_warn(CUT_HERE);
+
pr_err("UBSAN: %s in %s:%d:%d\n", reason, loc->file_name,
loc->line & LINE_MASK, loc->column & COLUMN_MASK);
@@ -215,8 +215,7 @@ static void ubsan_prologue(struct source
static void ubsan_epilogue(void)
{
dump_stack();
- pr_err("========================================"
- "========================================\n");
+ pr_warn("---[ end trace ]---\n");
current->in_ubsan--;
_
Patches currently in -mm which might be from bp@alien8.de are
reply other threads:[~2023-12-20 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231220224933.D37ACC433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=mm-commits@vger.kernel.org \
--cc=ryabinin.a.a@gmail.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.