From: Borislav Petkov <bp@suse.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 5.17-rc4
Date: Sun, 13 Feb 2022 13:37:17 +0100 [thread overview]
Message-ID: <Ygj7feK+vdtPw6zj@zn.tnic> (raw)
Hi Linus,
please pull a single urgent scheduling fix for 5.17.
Thx.
---
The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:
Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v5.17_rc4
for you to fetch changes up to 13765de8148f71fa795e0a6607de37c49ea5915a:
sched/fair: Fix fault in reweight_entity (2022-02-06 22:37:26 +0100)
----------------------------------------------------------------
- Fix a NULL-ptr dereference when recalculating a sched entity's weight
----------------------------------------------------------------
Tadeusz Struk (1):
sched/fair: Fix fault in reweight_entity
kernel/sched/core.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-02-13 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 12:37 Borislav Petkov [this message]
2022-02-13 18:02 ` [GIT PULL] sched/urgent for 5.17-rc4 Linus Torvalds
2022-02-14 8:45 ` Peter Zijlstra
2022-02-14 9:16 ` Peter Zijlstra
2022-02-14 19:17 ` Tejun Heo
2022-02-14 19:35 ` Peter Zijlstra
2022-02-14 19:46 ` Tejun Heo
2022-02-17 8:51 ` [PATCH] sched: Fix yet more sched_fork() races Peter Zijlstra
2022-02-17 10:50 ` Dietmar Eggemann
2022-02-17 12:08 ` Zhang Qiao
2022-02-17 17:33 ` Tadeusz Struk
2022-02-18 6:18 ` Zhang Qiao
2022-02-19 10:14 ` [tip: sched/urgent] " tip-bot2 for Peter Zijlstra
2022-02-13 18:04 ` [GIT PULL] sched/urgent for 5.17-rc4 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=Ygj7feK+vdtPw6zj@zn.tnic \
--to=bp@suse.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