public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: linux-kernel@vger.kernel.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/4] kernel/panic: add more descriptive logging of kernel taints
Date: Fri, 31 May 2024 12:04:53 +0300	[thread overview]
Message-ID: <cover.1717146197.git.jani.nikula@intel.com> (raw)

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


             reply	other threads:[~2024-05-31  9:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  9:04 Jani Nikula [this message]
2024-05-31  9:04 ` [PATCH 1/4] kernel/panic: return early from print_tainted() when not tainted Jani Nikula
2024-06-04 15:33   ` Greg KH
2024-05-31  9:04 ` [PATCH 2/4] kernel/panic: convert print_tainted() to use struct seq_buf internally Jani Nikula
2024-06-04 15:34   ` Greg KH
2024-05-31  9:04 ` [PATCH 3/4] kernel/panic: initialize taint_flags[] using a macro Jani Nikula
2024-06-04 15:34   ` Greg KH
2024-05-31  9:04 ` [PATCH 4/4] kernel/panic: add verbose logging of kernel taints in backtraces Jani Nikula
2024-06-04 15:34   ` Greg KH

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=cover.1717146197.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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