All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	Fernand Sieber <sieberf@amazon.com>
Subject: Re: Please add 127b90315ca0 ("sched/proxy: Yield the donor task") to 6.12.y / 6.18.y
Date: Fri, 2 Jan 2026 13:22:44 +0100	[thread overview]
Message-ID: <2026010235-contort-catwalk-835b@gregkh> (raw)
In-Reply-To: <04b82346-c38a-08e2-49d5-d64981eb7dae@applied-asynchrony.com>

On Tue, Dec 30, 2025 at 03:38:34PM +0100, Holger Hoffstätte wrote:
> Hi -
> 
> a Gentoo user recently found that 6.18.2 started to reproducuibly
> crash when building their go toolchain [1].
> 
> Apparently the addition of "sched/fair: Forfeit vruntime on yield"
> (mainline 79104becf42b) can result in the infamous NULL returned from
> pick_eevdf(), which is not supposed to happen.
> 
> It turned out that the mentioned commit triggered a bug related
> to the recently added proxy execution feature, which was already
> fixed in mainline by "sched/proxy: Yield the donor task"
> (127b90315ca0), though not marked for stable.
> 
> Applying this to 6.18.2/.3-rc1 (and probably 6.12 as well)
> has reproducibly fixed the problem. A possible reason the crash
> was triggered by the Go runtime could be its specific use of yield(),
> though that's just speculation on my part.
> 
> So please add 127b90315ca0 ("sched/proxy: Yield the donor task")
> to 6.18.y/6.12.y. I know we're already in 6.18.3-rc1, but the
> crasher seems reproducible.

Now queued up to 6.18.y, thanks.

greg k-h

      parent reply	other threads:[~2026-01-02 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 14:38 Please add 127b90315ca0 ("sched/proxy: Yield the donor task") to 6.12.y / 6.18.y Holger Hoffstätte
2025-12-30 23:45 ` Wang Yugui
2025-12-31 12:22   ` Holger Hoffstätte
2026-01-02 12:22 ` Greg KH [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=2026010235-contort-catwalk-835b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=holger@applied-asynchrony.com \
    --cc=sashal@kernel.org \
    --cc=sieberf@amazon.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.