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,
tanghui20@huawei.com, zhangqiao22@huawei.com,
judy.chenhui@huawei.com
Subject: Re: [PATCH] sched/fair: Fix overflow in vruntime_eligible() causing NULL return
Date: Thu, 10 Jul 2025 13:13:34 +0200 [thread overview]
Message-ID: <20250710111334.GD542000@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <d8588f5d-bccc-4791-9d44-bd3e383d21b9@huawei.com>
On Thu, Jul 10, 2025 at 10:01:15AM +0800, Zicheng Qu wrote:
> Hi,
>
> Based on LTS 6.6. I also looked at the code logic around vruntime_eligible()
> in the mainline. It seems that if vruntime_eligible() consistently returned
> false, this could lead to null pointer dereferences.
That is a truly ancient kernel. Please verify the issue is reproducible
on something recent.
Specifically, commit bbce3de72be5 ("sched/eevdf: Fix se->slice being set
to U64_MAX and resulting crash") cured something very similar to this.
next prev parent reply other threads:[~2025-07-10 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 9:38 [PATCH] sched/fair: Fix overflow in vruntime_eligible() causing NULL return Zicheng Qu
2025-07-09 11:53 ` Peter Zijlstra
2025-07-10 2:01 ` Zicheng Qu
2025-07-10 11:13 ` Peter Zijlstra [this message]
2025-08-07 3:06 ` Fang Xiang
-- strict thread matches above, loose matches on Subject: below --
2025-08-08 9:21 quzicheng
2026-01-06 11:34 Fang Xiang
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=20250710111334.GD542000@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=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 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.