From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org, npiggin@gmail.com,
tpearson@raptorengineering.com, daniel@mariadb.org,
linuxppc-dev@lists.ozlabs.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-3 tag
Date: Sun, 03 Dec 2023 10:12:23 +1100 [thread overview]
Message-ID: <87jzpw9p2g.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some powerpc fixes for 6.7:
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.7-3
for you to fetch changes up to dc158d23b33df9033bcc8e7117e8591dd2f9d125:
KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers (2023-11-29 22:24:21 +1100)
- ------------------------------------------------------------------
powerpc fixes for 6.7 #3
- Fix corruption of f0/vs0 during FP/Vector save, seen as userspace crashes
when using io-uring workers (in particular with MariaDB).
- Fix KVM_RUN potentially clobbering all host userspace FP/Vector registers.
Thanks to: Timothy Pearson, Jens Axboe, Nicholas Piggin.
- ------------------------------------------------------------------
Nicholas Piggin (1):
KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers
Timothy Pearson (1):
powerpc: Don't clobber f0/vs0 during fp|altivec register save
arch/powerpc/kernel/fpu.S | 13 +++++++++++++
arch/powerpc/kernel/process.c | 6 +++---
arch/powerpc/kernel/vector.S | 2 ++
3 files changed, 18 insertions(+), 3 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmVruPoACgkQUevqPMjh
pYBdlg//cW9CHahWFix93X5k3b+5LluRynR63BN4FnY+qVni95ihTxRC56rRpmUE
JfbgADz3fFgPdX4/XXnpkrMY7rDyrwTelNT1X5Dl6nwounrqBRvCvplfHrlAPZqR
C12ZBgbdJJmLucAtZv0mXsJ1NMiay9QZK7qIS7xJ22F7nEmnb5/BWs908hH6IwP0
pPOoi0AwiLqtsi6caIXr4GV1qoUbhfNOihZdXObCKetaOpEdcHUfu/vcNOhsVfgS
f8NbyOKZ+dLasCB5ifa5gVw7MQfj++ljLive5C2t51Y1v2I1C3KRhQdoZmTFvWZD
CXxRdCVfgrG5KWGXflG43pypYhmPcJSplDrP2Rg7EGFdasgl7Duc5VGh1l40p84k
Via0iNCJBzL+j6heq47a4TA+oJRAK1HtPjd+ZrP4Rx3sxlIR9IiKAO3i2s8i3Djh
nbK+BAxDBRlmE1+xOeplOsW5ZfjUVjv+mXHycGIGU//RGD8xOaX90USu1uBq2xbQ
UKEpAMwrgpuZpCj/+nWaaEj/SuorkfyZeSoIce3l70LpBZTEJFT5cNNexFW63q2p
QWcnnOxm3flS9tU+GOd/lFjAfV4AJSRKiagUk3JrIjGezl4HyXj6NXulZIIKvgVD
zzDTDEL4trP/Eh8x9JEAKs0qmoMHoqe0hBCsnKS9qSoBoUZQvkI=
=d6c4
-----END PGP SIGNATURE-----
next reply other threads:[~2023-12-02 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 23:12 Michael Ellerman [this message]
2023-12-02 23:52 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-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=87jzpw9p2g.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=axboe@kernel.dk \
--cc=daniel@mariadb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tpearson@raptorengineering.com \
/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