[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250226100730.3097dc38@gandalf.local.home>
Date: Wed, 26 Feb 2025 10:07:30 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>, Peter Zijlstra
<peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Will Deacon
<will@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Boqun Feng
<boqun.feng@...il.com>, Waiman Long <longman@...hat.com>, Joel Granados
<joel.granados@...nel.org>, Anna Schumaker <anna.schumaker@...cle.com>,
Lance Yang <ioworker0@...il.com>, Kent Overstreet
<kent.overstreet@...ux.dev>, Yongliang Gao <leonylgao@...cent.com>, Tomasz
Figa <tfiga@...omium.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/2] hung_task: Show the blocker task if the task is
hung on mutex
On Wed, 26 Feb 2025 13:38:19 +0900
Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
> I assume another possibility can be that the owner is still around,
> let's say a kworker that simply forgot to mutex_unlock(), so we'll
> get its backtrace but it can be misleading, because kworker in
> question might be doing something completely unrelated.
Well, if that happens, then we have much bigger problems than this ;-)
-- Steve
Powered by blists - more mailing lists