From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Rutland <mark.rutland@arm.com>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] core/entry for v5.17
Date: Mon, 10 Jan 2022 19:57:19 +0100 [thread overview]
Message-ID: <YdyBj2BpUyFa5ux8@zn.tnic> (raw)
Hi Linus,
please pull a separate thread_info.flags accessors conversion branch
which has been agreed upon to go through tip.
Thx.
---
The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:
Linux 5.16-rc3 (2021-11-28 14:09:19 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/core_entry_for_v5.17_rc1
for you to fetch changes up to 985faa78687de6e583cfd8b8094d87dcb80c33a6:
powerpc: Snapshot thread flags (2021-12-01 00:06:44 +0100)
----------------------------------------------------------------
- Add a set of thread_info.flags accessors which snapshot it before
accesing it in order to prevent any potential data races, and convert
all users to those new accessors
----------------------------------------------------------------
Mark Rutland (11):
thread_info: Add helpers to snapshot thread flags
x86: Snapshot thread flags
entry: Snapshot thread flags
sched: Snapshot thread flags
alpha: Snapshot thread flags
ARM: Snapshot thread flags
arm64: Snapshot thread flags
microblaze: Snapshot thread flags
openrisc: Snapshot thread flags
powerpc: Avoid discarding flags in system_call_exception()
powerpc: Snapshot thread flags
arch/alpha/kernel/signal.c | 2 +-
arch/arm/kernel/signal.c | 2 +-
arch/arm/mm/alignment.c | 2 +-
arch/arm64/kernel/entry-common.c | 2 +-
arch/arm64/kernel/ptrace.c | 4 ++--
arch/arm64/kernel/signal.c | 2 +-
arch/arm64/kernel/syscall.c | 4 ++--
arch/microblaze/kernel/signal.c | 2 +-
arch/openrisc/kernel/signal.c | 2 +-
arch/powerpc/kernel/interrupt.c | 15 +++++++--------
arch/powerpc/kernel/ptrace/ptrace.c | 3 +--
arch/x86/kernel/process.c | 8 ++++----
arch/x86/kernel/process.h | 4 ++--
arch/x86/mm/tlb.c | 2 +-
include/linux/entry-kvm.h | 2 +-
include/linux/thread_info.h | 14 ++++++++++++++
kernel/entry/common.c | 4 ++--
kernel/entry/kvm.c | 4 ++--
kernel/sched/core.c | 2 +-
19 files changed, 46 insertions(+), 34 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-01-10 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:57 Borislav Petkov [this message]
2022-01-10 19:48 ` 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=YdyBj2BpUyFa5ux8@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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®