From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rdunlap@infradead.org,peterz@infradead.org,jpoimboe@kernel.org,gpiccoli@igalia.com,feng.tang@intel.com,corbet@lwn.net,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] panic-add-option-to-dump-blocked-tasks-in-panic_print-fix.patch removed from -mm tree
Date: Thu, 22 Feb 2024 15:35:36 -0800 [thread overview]
Message-ID: <20240222233537.32F63C433F1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: panic-add-option-to-dump-blocked-tasks-in-panic_print-fix
has been removed from the -mm tree. Its filename was
panic-add-option-to-dump-blocked-tasks-in-panic_print-fix.patch
This patch was dropped because it was folded into panic-add-option-to-dump-blocked-tasks-in-panic_print.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: panic-add-option-to-dump-blocked-tasks-in-panic_print-fix
Date: Sat Feb 3 04:31:14 AM PST 2024
clarify documentation a little
Cc: Feng Tang <feng.tang@intel.com>
Cc: Guilherme G. Piccoli <gpiccoli@igalia.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/admin-guide/kernel-parameters.txt | 2 +-
Documentation/admin-guide/sysctl/kernel.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- a/Documentation/admin-guide/kernel-parameters.txt~panic-add-option-to-dump-blocked-tasks-in-panic_print-fix
+++ a/Documentation/admin-guide/kernel-parameters.txt
@@ -4182,7 +4182,7 @@
bit 4: print ftrace buffer
bit 5: print all printk messages in buffer
bit 6: print all CPUs backtrace (if available in the arch)
- bit 7: print tasks in uninterruptible (blocked) state
+ bit 7: print only tasks in uninterruptible (blocked) state
*Be aware* that this option may print a _lot_ of lines,
so there are risks of losing older messages in the log.
Use this option carefully, maybe worth to setup a
--- a/Documentation/admin-guide/sysctl/kernel.rst~panic-add-option-to-dump-blocked-tasks-in-panic_print-fix
+++ a/Documentation/admin-guide/sysctl/kernel.rst
@@ -853,7 +853,7 @@ bit 3 print locks info if ``CONFIG_LOCK
bit 4 print ftrace buffer
bit 5 print all printk messages in buffer
bit 6 print all CPUs backtrace (if available in the arch)
-bit 7 print tasks in uninterruptible (blocked) state
+bit 7 print only tasks in uninterruptible (blocked) state
===== ============================================
So for example to print tasks and memory info on panic, user can::
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
kexec-split-crashkernel-reservation-code-out-from-crash_corec-fix.patch
arch-crash-move-arch_crash_save_vmcoreinfo-out-to-file-vmcore_infoc-fix.patch
mm-swapfile-__swap_duplicate-drop-redundant-write_once-on-swap_map-for-err-cases-fix.patch
hugetlb-parallelize-1g-hugetlb-initialization-fix.patch
panic-add-option-to-dump-blocked-tasks-in-panic_print.patch
reply other threads:[~2024-02-22 23:35 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=20240222233537.32F63C433F1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=feng.tang@intel.com \
--cc=gpiccoli@igalia.com \
--cc=jpoimboe@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.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 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.