The patch titled
Subject: kasan: distinguish kasan report from generic BUG()
has been added to the -mm tree. Its filename is
kasan-distinguish-kasan-report-from-generic-bug.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/kasan-distinguish-kasan-report-from-generic-bug.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/kasan-distinguish-kasan-report-from-generic-bug.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Jiri Kosina <jkosina@xxxxxxx>
Subject: kasan: distinguish kasan report from generic BUG()
The typical KASAN report always begins with
BUG: KASAN: ....
in kernel log. That 'BUG:' prefix creates a false impression that it's an
actual BUG() codepath being executed, and as such things like
'panic_on_oops' etc. would work on it as expected; but that's obviously
not the case.
Switch the order of prefixes to make this distinction clear and avoid
confusion.
Link: https://lkml.kernel.org/r/nycvar.YFH.7.76.2111241839590.16505@xxxxxxxxxxxxx
Signed-off-by: Jiri Kosina <jkosina@xxxxxxx>
Cc: Andrey Ryabinin <ryabinin.a.a@xxxxxxxxx>
Cc: Alexander Potapenko <glider@xxxxxxxxxx>
Cc: Andrey Konovalov <andreyknvl@xxxxxxxxx>
Cc: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Cc: Jiri Slaby <jirislaby@xxxxxxxxxx>
Cc: Marco Elver <elver@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/kasan/report.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/mm/kasan/report.c~kasan-distinguish-kasan-report-from-generic-bug
+++ a/mm/kasan/report.c
@@ -86,7 +86,7 @@ __setup("kasan_multi_shot", kasan_set_mu
static void print_error_description(struct kasan_access_info *info)
{
- pr_err("BUG: KASAN: %s in %pS\n",
+ pr_err("KASAN: BUG: %s in %pS\n",
kasan_get_bug_type(info), (void *)info->ip);
if (info->access_size)
pr_err("%s of size %zu at addr %px by task %s/%d\n",
@@ -366,7 +366,7 @@ void kasan_report_invalid_free(void *obj
#endif /* IS_ENABLED(CONFIG_KUNIT) */
start_report(&flags);
- pr_err("BUG: KASAN: double-free or invalid-free in %pS\n", (void *)ip);
+ pr_err("KASAN: BUG: double-free or invalid-free in %pS\n", (void *)ip);
kasan_print_tags(tag, object);
pr_err("\n");
print_address_description(object, tag);
@@ -386,7 +386,7 @@ void kasan_report_async(void)
#endif /* IS_ENABLED(CONFIG_KUNIT) */
start_report(&flags);
- pr_err("BUG: KASAN: invalid-access\n");
+ pr_err("KASAN: BUG: invalid-access\n");
pr_err("Asynchronous mode enabled: no access details available\n");
pr_err("\n");
dump_stack_lvl(KERN_ERR);
_
Patches currently in -mm which might be from jkosina@xxxxxxx are
kasan-distinguish-kasan-report-from-generic-bug.patch
