From: Peter Zijlstra <peterz@infradead.org>
To: Zicheng Qu <quzicheng@huawei.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, linux-kernel@vger.kernel.org,
wulibin163@126.com, tanghui20@huawei.com, zhangqiao22@huawei.com,
judy.chenhui@huawei.com
Subject: Re: [PATCH EEVDF NULL deref] sched/eevdf: Fix NULL deref when avg_vruntime nears overflow
Date: Wed, 5 Nov 2025 13:39:54 +0100 [thread overview]
Message-ID: <20251105123954.GM3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <7cdcc98e-990e-4408-ba75-57dd0229316e@huawei.com>
On Wed, Nov 05, 2025 at 06:47:40PM +0800, Zicheng Qu wrote:
> This is the reproduction patch. We encountered a similar issue on a
> normally running kernel, and after analysis, we deliberately constructed
> a comparable scenario. Since it is difficult to control the conditions
> from user space, we proactively modified certain parts of the kernel
> code to simulate the issue (the code includes detailed explanations).
Thanks!
> As for the zero_vruntime patch, after applying it, we have not
> observed any crashes over than 24 hours.
Excellent, I'll go think about the SCHED_CORE case and make it a proper
patch then.
next prev parent reply other threads:[~2025-11-05 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 13:04 Zicheng Qu
2025-11-03 20:26 ` Peter Zijlstra
2025-11-05 10:47 ` Zicheng Qu
2025-11-05 12:39 ` Peter Zijlstra [this message]
2025-11-06 11:16 ` Peter Zijlstra
2025-11-06 11:17 ` Peter Zijlstra
2025-11-11 11:37 ` [tip: sched/core] sched/eevdf: Fix min_vruntime vs avg_vruntime tip-bot2 for Peter Zijlstra
2025-11-11 11:37 ` [tip: sched/core] sched/core: Add comment explaining force-idle vruntime snapshots tip-bot2 for Peter Zijlstra
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=20251105123954.GM3245006@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=judy.chenhui@huawei.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=quzicheng@huawei.com \
--cc=rostedt@goodmis.org \
--cc=tanghui20@huawei.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wulibin163@126.com \
--cc=zhangqiao22@huawei.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®