From: Han Guangjiang <gj.han@foxmail.com>
To: peterz@infradead.org
Cc: bsegall@google.com, dietmar.eggemann@arm.com,
fanggeng@lixiang.com, gj.han@foxmail.com,
hanguangjiang@lixiang.com, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@redhat.com,
rostedt@goodmis.org, vincent.guittot@linaro.org,
vschneid@redhat.com, yangchen11@lixiang.com
Subject: Re: [PATCH] sched/fair: Fix DELAY_DEQUEUE issue related to cgroup throttling
Date: Wed, 1 Oct 2025 09:15:27 +0800 [thread overview]
Message-ID: <tencent_46288A6EC6007C3C980C22DB856268526209@qq.com> (raw)
In-Reply-To: <20250930125621.GO3419281@noisy.programming.kicks-ass.net>
>> From: Han Guangjiang <hanguangjiang@lixiang.com>
>>
>> When both CPU cgroup and memory cgroup are enabled with parent cgroup
>> resource limits much smaller than child cgroup's, the system frequently
>> hangs with NULL pointer dereference:
>>
> Is this the same issue as here:
>
> https://lore.kernel.org/all/105ae6f1-f629-4fe7-9644-4242c3bed035@amd.com/T/#u
>
> ?
Yes, based on the patch modifications, I believe this is the same issue.
When dequeue_entities() is executed on a delay_dequeued task while the
cgroup is being throttled, it returns early and misses the
__block_task() operation on the task. This leads to inconsistency
between p->on_rq and se->on_rq.
When PI or scheduler switching occurs, the second dequeue_entities()
call assumes the task is still in the CFS scheduler, but in reality
it is no longer there.
By the way, I have a question about the hrtick_update() in
dequeue_entities(). Should it be changed to:
dequeue_entities()
{
...
if (p) {
hrtick_update(rq);
}
...
}
And remove hrtick_update() from dequeue_task_fair()?
Because for dequeue_delayed tasks, hrtick_update() will be executed
twice in this proces.
Also, should the return type of dequeue_entities() be changed to
match dequeue_task_fair(), where true means the task was actually
removed from the queue, and false means it was delay dequeued?
Thanks,
Han Guangjiang
prev parent reply other threads:[~2025-10-01 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 1:51 Han Guangjiang
2025-09-30 12:30 ` Pierre Gondois
2025-10-01 0:49 ` Han Guangjiang
2025-09-30 12:56 ` Peter Zijlstra
2025-10-01 1:15 ` Han Guangjiang [this message]
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=tencent_46288A6EC6007C3C980C22DB856268526209@qq.com \
--to=gj.han@foxmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=fanggeng@lixiang.com \
--cc=hanguangjiang@lixiang.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yangchen11@lixiang.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®