mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sched/urgent for v6.18-rc3
Date: Sun, 26 Oct 2025 12:49:25 +0100	[thread overview]
Message-ID: <20251026114925.GAaP4KxfT1-DpmVBpp@fat_crate.local> (raw)

Hi Linus,

please pull a sched/urgent fix for v6.18-rc3.

Thx.

---

The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:

  Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/sched_urgent_for_v6.18_rc3

for you to fetch changes up to 0e4a169d1a2b630c607416d9e3739d80e176ed67:

  sched/fair: Start a cfs_rq on throttled hierarchy with PELT clock throttled (2025-10-22 15:21:52 +0200)

----------------------------------------------------------------
- Make sure a CFS runqueue on a throttled hierarchy has its PELT clock
  throttled otherwise task movement and manipulation would lead to dangling
  cfs_rq references and an eventual crash

----------------------------------------------------------------
K Prateek Nayak (1):
      sched/fair: Start a cfs_rq on throttled hierarchy with PELT clock throttled

 kernel/sched/fair.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2025-10-26 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26 11:49 Borislav Petkov [this message]
2025-10-26 17:00 ` pr-tracker-bot

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=20251026114925.GAaP4KxfT1-DpmVBpp@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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 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®