From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
npiggin@gmail.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.16-3 tag
Date: Sat, 27 Nov 2021 20:51:41 +1100 [thread overview]
Message-ID: <87ilweoriq.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.16:
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.16-3
for you to fetch changes up to 5bb60ea611db1e04814426ed4bd1c95d1487678e:
powerpc/32: Fix hardlockup on vmap stack overflow (2021-11-24 21:00:51 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.16 #3
Fix KVM using a Power9 instruction on earlier CPUs, which could lead to the host SLB being
incorrectly invalidated and a subsequent host crash.
Fix kernel hardlockup on vmap stack overflow on 32-bit.
Thanks to: Christophe Leroy, Nicholas Piggin, Fabiano Rosas.
- ------------------------------------------------------------------
Christophe Leroy (1):
powerpc/32: Fix hardlockup on vmap stack overflow
Nicholas Piggin (1):
KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
arch/powerpc/kernel/head_32.h | 6 +++---
arch/powerpc/kvm/book3s_hv_builtin.c | 5 ++++-
2 files changed, 7 insertions(+), 4 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmGh/0IACgkQUevqPMjh
pYC11A//aE4RsEdrvL3TY3oEWmDoDC3xtrKub5TCopudvWubpSHEvsUzCjyLPmeO
s/5pllifG8s9LKFHqwCTTLWnfqaZkTcQMF2THLM7gGT4BjYRS0snjcXbVNaaCeNr
ByvZduLjfoGsUkWeKojQ3Kc+xAOU1oQPJfiAofyRQtUYfirYMSA89I0wXImzhEad
/vy6galPLtFXjEJiBVzLjqVFnmTMML4pHHQMF7F0pposxQNvWA73VYeov14kz98G
sOElGv3U168gd4sNsVbN3imUo5dmoOSriH+MtZEKRYMznbvb/Lq8/RvF7MXhJdlw
iTpMAuCNiCDJzn9yUJ4nRu3CEimaznN04sP107D4YEHDERDvVQoyFE6kGaT1NUsF
bIhWRU7gLURJrVNAZeabtTYa90pHdFdHIs3eNUTHW8Fyowf6Gr4CD8MZ1kb+A/wB
1MNLaOjfkOltbar/KtWz+sNpvnu8GeSUrK4bSBWyJAhDLHds250XQ6ZJcjRCtFKT
sk7sefle5nV8o2MStYQQ0i88n0ZKm3wdpAFoHgWry713p2ECZ1sWopiVDZZwxK/2
Pt94JncFV+RNG5uIf9RmXauU+R+zWIHVstiiwz5ZIOFKE6dtSwaD6BdoMuh4zNP5
fXL86D3cnhwk2F0r1kPjznjZzDFERsNMOHYkI8C8twvE/NklN1Y=
=5saw
-----END PGP SIGNATURE-----
next reply other threads:[~2021-11-27 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 9:51 Michael Ellerman [this message]
2021-11-27 18:58 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.16-3 tag 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=87ilweoriq.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).