mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Jirka Hladky <jhladky@redhat.com>,
	Abhigyan ghosh <zscript.team.zs@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, Chen Yu <yu.chen.surf@foxmail.com>
Subject: Re: [BUG] Kernel panic in __migrate_swap_task() on 6.16-rc2 (NULL pointer dereference)
Date: Fri, 27 Jun 2025 15:33:29 +0800	[thread overview]
Message-ID: <d0b7b52b-c370-4ad7-8a03-d785f1505372@intel.com> (raw)
In-Reply-To: <31bd3395-cfe3-4af5-bc1c-fa8d26629b93@intel.com>

On 6/27/2025 3:16 PM, Chen, Yu C wrote:
> Hi Jirka,
> 
> On 6/27/2025 5:46 AM, Jirka Hladky wrote:
>> Hi Chen and all,
>>
>> we have now verified that the following commit causes a kernel panic
>> discussed in this thread:
>>
>> ad6b26b6a0a79 sched/numa: add statistics of numa balance task
>>
>> Reverting this commit fixes the issue.
>>
>> I'm happy to help debug this further or test a proposed fix.
>>
> 
> Thanks very much for your report, it seems that there is a
> race condition that when the swap task candidate was chosen,
> but its mm_struct get released due to task exit, then later
> when doing the task swaping, the p->mm is NULL which caused
> the problem:
> 
> CPU0                                   CPU1
> :
> ...
> task_numa_migrate
>    task_numa_find_cpu
>     task_numa_compare
>       # a normal task p is chosen
>       env->best_task = p
> 
>                                         # p exit:
>                                         exit_signals(p);
>                                            p->flags |= PF_EXITING
>                                         exit_mm
>                                            p->mm = NULL;
> 
>     migrate_swap_stop
>       __migrate_swap_task((arg->src_task, arg->dst_cpu)
>        count_memcg_event_mm(p->mm, NUMA_TASK_SWAP)# p->mm is NULL
> 
> Could you please help check if the following debug patch works,

Attached the patch:

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 8988d38d46a3..82fc966b390c 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3364,7 +3364,12 @@ static void __migrate_swap_task(struct 
task_struct *p, int cpu)
  {
  	__schedstat_inc(p->stats.numa_task_swapped);
  	count_vm_numa_event(NUMA_TASK_SWAP);
-	count_memcg_event_mm(p->mm, NUMA_TASK_SWAP);
+	if (unlikely(!p->mm)) {
+		trace_printk("!! (%d %s) flags=%lx\n", p->pid, p->comm,
+				p->flags);
+	} else {
+		count_memcg_event_mm(p->mm, NUMA_TASK_SWAP);
+	}

  	if (task_on_rq_queued(p)) {
  		struct rq *src_rq, *dst_rq;
-- 
2.25.1

> and if there is no issue found after you ran several tests,
> could you please provide the
> /sys/kernel/debug/tracing/trace
> 
> BTW, is it possible to share your test script for stress-ng,
> stream? It looks like the stress-ng's fork test case would
> trigger this issue easier in theory.
> 
> thanks,
> Chenyu
> 
> 

  reply	other threads:[~2025-06-27  7:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 20:05 Jirka Hladky
2025-06-18  4:43 ` Aithal, Srikanth
2025-06-18  5:19 ` Abhigyan ghosh
2025-06-18 11:34   ` Jirka Hladky
2025-06-26 21:46     ` Jirka Hladky
2025-06-27  7:16       ` Chen, Yu C
2025-06-27  7:33         ` Chen, Yu C [this message]
2025-07-01  7:32           ` Libo Chen
2025-07-01 14:59             ` Chen, Yu C
2025-07-01 15:10               ` Jirka Hladky
2025-07-01 21:05                 ` Jirka Hladky
2025-07-02 11:14                   ` Chen, Yu C
2025-07-02 11:43                     ` Jirka Hladky
2025-07-02  4:32           ` Aithal, Srikanth
2025-07-02  7:36             ` Aithal, Srikanth
2025-07-02 11:17               ` Chen, Yu C
2025-07-02 11:53                 ` Jirka Hladky
2025-07-02 12:19                   ` Aithal, Srikanth
2025-07-02 13:24                     ` Jirka Hladky
2025-07-03 23:50                       ` Jirka Hladky
2025-06-27 10:48         ` Jirka Hladky

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=d0b7b52b-c370-4ad7-8a03-d785f1505372@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=jhladky@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yu.chen.surf@foxmail.com \
    --cc=zscript.team.zs@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®