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.2-rc6
Date: Sun, 22 Jan 2023 13:18:50 +0100	[thread overview]
Message-ID: <Y80pqpsa/f2eEcYP@zn.tnic> (raw)

Hi Linus,

please pull a couple of urgent scheduler fixes for 6.2.

Thx.

---

The following changes since commit 9a5418bc48babb313d2a62df29ebe21ce8c06c59:

  sched/core: Use kfree_rcu() in do_set_cpus_allowed() (2023-01-09 11:43:23 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v6.2_rc6

for you to fetch changes up to 5f5cc9ed992cbab6361f198966f0edba5fc52688:

  x86/aperfmperf: Erase stale arch_freq_scale values when disabling frequency invariance readings (2023-01-16 10:19:15 +0100)

----------------------------------------------------------------
- Make sure the scheduler doesn't use stale frequency scaling values when latter
  get disabled due to a value error

- Fix a NULL pointer access on UP configs

- Use the proper locking when updating CPU capacity

----------------------------------------------------------------
Qais Yousef (2):
      sched/uclamp: Fix a uninitialized variable warnings
      sched/fair: Fixes for capacity inversion detection

Waiman Long (1):
      sched/core: Fix NULL pointer access fault in sched_setaffinity() with non-SMP configs

Yair Podemsky (1):
      x86/aperfmperf: Erase stale arch_freq_scale values when disabling frequency invariance readings

 arch/x86/kernel/cpu/aperfmperf.c |  9 ++++++++
 kernel/sched/core.c              | 10 +++++++--
 kernel/sched/fair.c              | 48 ++++++++++++++++++++++------------------
 3 files changed, 44 insertions(+), 23 deletions(-)

-- 
Regards/Gruss,
    Boris.

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

             reply	other threads:[~2023-01-22 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 12:18 Borislav Petkov [this message]
2023-01-22 20:20 ` 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=Y80pqpsa/f2eEcYP@zn.tnic \
    --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®