From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Omar Sandoval <osandov@osandov.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12] sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash
Date: Fri, 9 May 2025 06:51:05 -0400 [thread overview]
Message-ID: <20250508145402-e4369d956fad8683@stable.kernel.org> (raw)
In-Reply-To: <9c0ce2024e862b3ee99bda8c16fbe9d863a9b918.1746650111.git.osandov@fb.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: bbce3de72be56e4b5f68924b7da9630cc89aa1a8
WARNING: Author mismatch between patch and upstream commit:
Backport author: Omar Sandoval<osandov@osandov.com>
Commit author: Omar Sandoval<osandov@fb.com>
Status in newer kernel trees:
6.14.y | Present (different SHA1: 50a665496881)
Note: The patch differs from the upstream commit:
---
1: bbce3de72be56 ! 1: 878496a829cec sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash
@@ Metadata
## Commit message ##
sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash
+ commit bbce3de72be56e4b5f68924b7da9630cc89aa1a8 upstream.
+
There is a code path in dequeue_entities() that can set the slice of a
sched_entity to U64_MAX, which sometimes results in a crash.
@@ Commit message
## kernel/sched/fair.c ##
@@ kernel/sched/fair.c: static int dequeue_entities(struct rq *rq, struct sched_entity *se, int flags)
- h_nr_idle = task_has_idle_policy(p);
- if (task_sleep || task_delayed || !se->sched_delayed)
- h_nr_runnable = 1;
+ idle_h_nr_running = task_has_idle_policy(p);
+ if (!task_sleep && !task_delayed)
+ h_nr_delayed = !!se->sched_delayed;
- } else {
- cfs_rq = group_cfs_rq(se);
- slice = cfs_rq_min_slice(cfs_rq);
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
prev parent reply other threads:[~2025-05-09 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 20:38 [PATCH 6.12] sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash Omar Sandoval
2025-05-09 10:51 ` Sasha Levin [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=20250508145402-e4369d956fad8683@stable.kernel.org \
--to=sashal@kernel.org \
--cc=osandov@osandov.com \
--cc=stable@vger.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.