From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,pmladek@suse.com,mhiramat@kernel.org,lance.yang@linux.dev,wangxb12@chinatelecom.cn,akpm@linux-foundation.org
Subject: + hung_task-update-detect_hung_task_blocker-kconfig-help.patch added to mm-nonmm-unstable branch
Date: Thu, 30 Jul 2026 13:32:08 -0700 [thread overview]
Message-ID: <20260730203209.3C20F1F000E9@smtp.kernel.org> (raw)
The patch titled
Subject: hung_task: update DETECT_HUNG_TASK_BLOCKER Kconfig help
has been added to the -mm mm-nonmm-unstable branch. Its filename is
hung_task-update-detect_hung_task_blocker-kconfig-help.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/hung_task-update-detect_hung_task_blocker-kconfig-help.patch
This patch will later appear in the mm-nonmm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
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 via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Xibo Wang <wangxb12@chinatelecom.cn>
Subject: hung_task: update DETECT_HUNG_TASK_BLOCKER Kconfig help
Date: Thu, 30 Jul 2026 14:18:54 +0800
The help text still says the feature only covers mutexes, but blocker
tracking has since been extended to semaphores and rwsems. Update the
description to match the supported lock types.
Link: https://lore.kernel.org/20260730061854.176547-1-wangxb12@chinatelecom.cn
Cc: Petr Mladek <pmladek@suse.com>
Signed-off-by: Xibo Wang <wangxb12@chinatelecom.cn>
Suggested-by: Lance Yang <lance.yang@linux.dev>
Reviewed-by: Lance Yang <lance.yang@linux.dev>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Petr Mladek <pmladek@suse.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/Kconfig.debug | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/lib/Kconfig.debug~hung_task-update-detect_hung_task_blocker-kconfig-help
+++ a/lib/Kconfig.debug
@@ -1292,10 +1292,10 @@ config DETECT_HUNG_TASK_BLOCKER
depends on !PREEMPT_RT
default y
help
- Say Y here to show the blocker task's stacktrace who acquires
- the mutex lock which "hung tasks" are waiting.
- This will add overhead a bit but shows suspicious tasks and
- call trace if it comes from waiting a mutex.
+ Say Y here to show a possible blocker task's stacktrace when
+ a hung task is waiting on a mutex, semaphore, or rwsem.
+ This will add a bit of overhead but shows suspicious tasks and
+ call traces for waits on one of these locks.
config WQ_WATCHDOG
bool "Detect Workqueue Stalls"
_
Patches currently in -mm which might be from wangxb12@chinatelecom.cn are
hung_task-update-detect_hung_task_blocker-kconfig-help.patch
reply other threads:[~2026-07-30 20:32 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=20260730203209.3C20F1F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=lance.yang@linux.dev \
--cc=mhiramat@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=wangxb12@chinatelecom.cn \
/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.