[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250414143804.e05de499b378f4da4cdc5f59@linux-foundation.org>
Date: Mon, 14 Apr 2025 14:38:04 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lance Yang <ioworker0@...il.com>
Cc: will@...nel.org, peterz@...radead.org, mingo@...hat.com,
longman@...hat.com, mhiramat@...nel.org, anna.schumaker@...cle.com,
boqun.feng@...il.com, joel.granados@...nel.org, kent.overstreet@...ux.dev,
leonylgao@...cent.com, linux-kernel@...r.kernel.org, rostedt@...dmis.org,
senozhatsky@...omium.org, tfiga@...omium.org, amaindex@...look.com,
jstultz@...gle.com
Subject: Re: [PATCH v5 0/3] hung_task: extend blocking task stacktrace dump
to semaphore
On Mon, 14 Apr 2025 22:59:42 +0800 Lance Yang <ioworker0@...il.com> wrote:
> Inspired by mutex blocker tracking[1], this patch series extend the
> feature to not only dump the blocker task holding a mutex but also to
> support semaphores. Unlike mutexes, semaphores lack explicit ownership
> tracking, making it challenging to identify the root cause of hangs. To
> address this, we introduce a last_holder field to the semaphore structure,
> which is updated when a task successfully calls down() and cleared during
> up().
Thanks, I'll queue this series in mm.git's mm-nonmm-unstable branch for
some test and exposure.
Powered by blists - more mailing lists