All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ridong Chen <ridong.chen@linux.dev>
To: "Farhad Alemi" <farhad.alemi@berkeley.edu>,
	"Waiman Long" <longman@redhat.com>, "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>
Cc: falemi@asu.edu, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] general protection fault in cpuset_cpus_allowed
Date: Fri, 28 Aug 2026 17:54:46 +0800	[thread overview]
Message-ID: <15c4ce09-ae6f-477e-a400-6b61fe81b477@linux.dev> (raw)
In-Reply-To: <dc5ce72e-b835-4ae2-b4c9-e96dc6d48eba@linux.dev>



On 8/28/2026 5:21 PM, Ridong Chen wrote:
> 
> 
> On 8/28/2026 1:43 PM, Farhad Alemi wrote:
>> Hello,
>>
>> As part of the kernel research at ASU's SEFCOM
>> lab, we hit the crash below. Crash reports can be found here:
>>
>>    https://github.com/farhad-alemi/public_bug_reports/tree/main/166-general- 
>> protection-fault-in-cpuset-cpus-allowed/
>>
>>    Oops: general protection fault, probably for non-canonical address
>> 0xdffffc000000001d: 0000 [#1] SMP KASAN NOPTI
>>    KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]
>>    RIP: 0010:bitmap_intersects include/linux/bitmap.h:440 [inline]
>>    RIP: 0010:cpumask_intersects include/linux/cpumask.h:822 [inline]
>>    RIP: 0010:guarantee_active_cpus kernel/cgroup/cpuset.c:481 [inline]
>>    RIP: 0010:__cpuset_cpus_allowed_locked kernel/cgroup/cpuset.c:4022 [inline]
>>    RIP: 0010:cpuset_cpus_allowed+0x14a/0x2f0 kernel/cgroup/cpuset.c:4071
>>    Call Trace:
>>     cpuset_cpus_allowed+0x14a/0x2f0 kernel/cgroup/cpuset.c:4071
>>     __sched_setaffinity+0x98/0x3c0 kernel/sched/syscalls.c:1149
>>     sched_setaffinity+0x341/0x4a0 kernel/sched/syscalls.c:1237
>>     __x64_sys_sched_setaffinity+0x106/0x170 kernel/sched/syscalls.c:1262
>>
>> A second capture reaches the identical fault -- same address, same KASAN range,
>> same RIP -- through cpuset_fork <- cgroup_post_fork <- copy_process <-
>> kernel_clone <- clone3, with the crashing task being systemd at PID 1.
>>
>> Our reproducer.c is available upon request.
>>
> 
> Thank you for the report.
> 
> Could you please share the reproducer.c with us?
> 

I suspect this might be caused by cs becoming NULL when cs = parent_cs(top_cpuset).

Having the reproducer would help me debug how this situation could occur.

```
static void guarantee_active_cpus(struct task_struct *tsk,
				  struct cpumask *pmask)
{
...
             while (!cpumask_intersects(cs->effective_cpus, pmask))
                     cs = parent_cs(cs);
...
}
```

>> Happy to test a patch if that would help.
>>
>> Regards,
> 

-- 
Best regards
Ridong


  reply	other threads:[~2026-08-28  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  5:43 [BUG] general protection fault in cpuset_cpus_allowed Farhad Alemi
2026-08-28  9:21 ` Ridong Chen
2026-08-28  9:54   ` Ridong Chen [this message]
2026-08-28 18:07 ` Waiman Long

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=15c4ce09-ae6f-477e-a400-6b61fe81b477@linux.dev \
    --to=ridong.chen@linux.dev \
    --cc=cgroups@vger.kernel.org \
    --cc=falemi@asu.edu \
    --cc=farhad.alemi@berkeley.edu \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    /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.