[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1717146197.git.jani.nikula@intel.com>
Date: Fri, 31 May 2024 12:04:53 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: linux-kernel@...r.kernel.org
Cc: jani.nikula@...el.com
Subject: [PATCH 0/4] kernel/panic: add more descriptive logging of kernel taints
Resend of
https://lore.kernel.org/r/cover.1711380724.git.jani.nikula@intel.com
A few years back there was a discussion about it being difficult to
remember all the taint flags [1].
Time flies. I stumbled on my old branch, brushed it up, and here it is.
I'm not entirely happy with the static buf (which was there to begin
with) or how to decide on its size. Thoughts?
BR,
Jani.
[1] https://lore.kernel.org/r/YmvU+/RUhOcL+B1p@kroah.com
Jani Nikula (4):
kernel/panic: return early from print_tainted() when not tainted
kernel/panic: convert print_tainted() to use struct seq_buf internally
kernel/panic: initialize taint_flags[] using a macro
kernel/panic: add verbose logging of kernel taints in backtraces
include/linux/panic.h | 8 +--
kernel/panic.c | 116 ++++++++++++++++++++++++++++--------------
lib/dump_stack.c | 3 ++
3 files changed, 87 insertions(+), 40 deletions(-)
--
2.39.2
Powered by blists - more mailing lists