[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYI3pzddATnKSbvZ@arm.com>
Date: Tue, 3 Feb 2026 18:00:07 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Zhongqiu Han <zhongqiu.han@....qualcomm.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mm/kmemleak: Use PF_KTHREAD flag to detect kernel
threads
On Fri, Jan 30, 2026 at 05:37:29PM +0800, Zhongqiu Han wrote:
> Replace the current->mm check with PF_KTHREAD flag for more reliable
> kernel thread detection in scan_should_stop(). The PF_KTHREAD flag is the
> standard way to identify kernel threads and is not affected by temporary
> mm borrowing via use_mm() (although kmemleak does not currently encounter
> such cases, this makes the code more robust).
Nitpick: it's called kthread_use_mm() now.
But you are right, this function is either called in a user thread
context (via a sysfs write) or from the kthread that kmemleak created
which would not use kthread_use_mm().
> No functional change.
>
> Signed-off-by: Zhongqiu Han <zhongqiu.han@....qualcomm.com>
> ---
> mm/kmemleak.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index fb0022f34393..eb2ffbaf2f7e 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -1507,10 +1507,10 @@ static int scan_should_stop(void)
> * This function may be called from either process or kthread context,
> * hence the need to check for both stop conditions.
> */
> - if (current->mm)
> - return signal_pending(current);
> + if (current->flags & PF_KTHREAD)
> + return kthread_should_stop();
>
> - return kthread_should_stop();
> + return signal_pending(current);
Acked-by: Catalin Marinas <catalin.marinas@....com>
Powered by blists - more mailing lists