From: Peter Schneider <pschneider1968@googlemail.com>
To: Sasha Levin <sashal@kernel.org>,
Brett A C Sheffield <bacs@librecast.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.12 0000/1102] 6.12.111-rc1 review
Date: Fri, 18 Sep 2026 22:45:24 +0200 [thread overview]
Message-ID: <8c3677b0-4def-42d8-989f-b0934c686f6f@googlemail.com> (raw)
In-Reply-To: <20260918151140.2101477305-sashal@kernel.org>
Am 18.09.2026 um 17:54 schrieb Sasha Levin:
> On Fri, Sep 18, 2026 at 07:49:48AM +0200, Peter Schneider wrote:
>> So I have bisected this warning, and the first bad commit is
>>
>> [af5775004c9c02f37be06d2035a056b6abb1cb6c] sched/fair: Fix EEVDF entity
>> placement bug causing scheduling lag
>
> Thank you - a second bisect on top of a reverted tree is real work, and
> it was the right call. Dropped from the 6.12 queue:
>
> 6d71a9c61604 ("sched/fair: Fix EEVDF entity placement bug causing
> scheduling lag")
>
>> Trying to revert this from 6.12.111-rc1 however resulted in some
>> conflicts I was unable to resolve. There are other dependencies like:
>
> Right, which is why the three patches stacked on top of it came out at
> the same time:
>
> 6e3c0a4e1ad1 ("sched/fair: Fix lag clamp")
> 51b0e68cfa0a ("sched/eevdf: Fix rb augmented with multi fields")
> 9a8bc9bb4c3f ("sched/eevdf: Fix augmented max_slice")
Ah ok, that third one I missed, so it didn't work out for me.
> Some background on why this only bites 6.12: the WARN_ON_ONCE(!load) you hit
> needs 4423af84b297 ("sched/fair: optimize the PLACE_LAG when se->vlag is zero")
> and c70fc32f4443 ("sched/fair: Adhere to place_entity() constraints", which is
> a Fixes: for exactly this commit) to be shut up, and 6.12 has neither. More to
> the point, upstream has since reverted 6d71a9c61604 outright - 101f3498b4bd
> ("sched/fair: Revert 6d71a9c61604 ...") from January, which concludes the
> original commit "was wrong!" because avg_vruntime() already accounts for
> cfs_rq->curr when it is on_rq. 6.12 only ever picked it up as a dependency of
> the eevdf fixes above, so carrying placement math that mainline has disowned is
> not something we want here.
Sounds complicated; no wonder I was unable to figure this out on my own.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
next prev parent reply other threads:[~2026-09-18 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:59 Greg Kroah-Hartman
2026-09-17 16:57 ` Florian Fainelli
2026-09-17 19:11 ` Peter Schneider
2026-09-17 20:21 ` Pavel Machek
2026-09-18 15:54 ` Sasha Levin
2026-09-17 19:35 ` Brett A C Sheffield
2026-09-17 20:19 ` Peter Schneider
2026-09-18 5:49 ` Peter Schneider
2026-09-18 15:54 ` Sasha Levin
2026-09-18 20:45 ` Peter Schneider [this message]
2026-09-18 15:54 ` Sasha Levin
2026-09-18 15:54 ` Sasha Levin
2026-09-17 20:18 ` Pavel Machek
2026-09-18 11:27 ` Jon Hunter
2026-09-18 15:54 ` Sasha Levin
2026-09-18 15:54 ` Sasha Levin
2026-09-18 7:16 ` [PATCH 6.18 0000/1250] 6.18.53-rc1 review Wentao Guan
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=8c3677b0-4def-42d8-989f-b0934c686f6f@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bacs@librecast.net \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 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®