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 6.1-rc6
Date: Sun, 20 Nov 2022 12:52:05 +0100 [thread overview]
Message-ID: <Y3oU5cB9LOcBLfSS@zn.tnic> (raw)
Hi Linus,
please pull two urgent scheduler fixes for 6.1.
Thx.
---
The following changes since commit 094226ad94f471a9f19e8f8e7140a09c2625abaa:
Linux 6.1-rc5 (2022-11-13 13:12:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v6.1_rc6
for you to fetch changes up to 91dabf33ae5df271da63e87ad7833e5fdb4a44b9:
sched: Fix race in task_call_func() (2022-11-14 09:58:32 +0100)
----------------------------------------------------------------
- Fix a small race on the task's exit path where there's a
misunderstanding whether the task holds rq->lock or not
- Prevent processes from getting killed when using deprecated or unknown
rseq ABI flags in order to be able to fuzz the rseq() syscall with
syzkaller
----------------------------------------------------------------
Mathieu Desnoyers (1):
rseq: Use pr_warn_once() when deprecated/unknown ABI flags are encountered
Peter Zijlstra (1):
sched: Fix race in task_call_func()
kernel/rseq.c | 19 +++++++++++++++++--
kernel/sched/core.c | 52 +++++++++++++++++++++++++++++++++++-----------------
2 files changed, 52 insertions(+), 19 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-11-20 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 11:52 Borislav Petkov [this message]
2022-11-20 18:52 ` [GIT PULL] sched/urgent for 6.1-rc6 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=Y3oU5cB9LOcBLfSS@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 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.