From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sasha Levin <sashal@kernel.org>,
frankja@linux.ibm.com, gor@linux.ibm.com, kvm@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: [PATCH AUTOSEL 6.6 06/19] KVM: s390: fix setting of fpc register
Date: Mon, 15 Jan 2024 20:05:01 -0500 [thread overview]
Message-ID: <20240116010532.218428-6-sashal@kernel.org> (raw)
In-Reply-To: <20240116010532.218428-1-sashal@kernel.org>
From: Heiko Carstens <hca@linux.ibm.com>
[ Upstream commit b988b1bb0053c0dcd26187d29ef07566a565cf55 ]
kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control
(fpc) register of a guest cpu. The new value is tested for validity by
temporarily loading it into the fpc register.
This may lead to corruption of the fpc register of the host process:
if an interrupt happens while the value is temporarily loaded into the fpc
register, and within interrupt context floating point or vector registers
are used, the current fp/vx registers are saved with save_fpu_regs()
assuming they belong to user space and will be loaded into fp/vx registers
when returning to user space.
test_fp_ctl() restores the original user space / host process fpc register
value, however it will be discarded, when returning to user space.
In result the host process will incorrectly continue to run with the value
that was supposed to be used for a guest cpu.
Fix this by simply removing the test. There is another test right before
the SIE context is entered which will handles invalid values.
This results in a change of behaviour: invalid values will now be accepted
instead of that the ioctl fails with -EINVAL. This seems to be acceptable,
given that this interface is most likely not used anymore, and this is in
addition the same behaviour implemented with the memory mapped interface
(replace invalid values with zero) - see sync_regs() in kvm-s390.c.
Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
arch/s390/kvm/kvm-s390.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index b3f17e014cab..49cce436444e 100644
--- a/arch/s390/kvm/kvm-s390.c
+++ b/arch/s390/kvm/kvm-s390.c
@@ -4307,10 +4307,6 @@ int kvm_arch_vcpu_ioctl_set_fpu(struct kvm_vcpu *vcpu, struct kvm_fpu *fpu)
vcpu_load(vcpu);
- if (test_fp_ctl(fpu->fpc)) {
- ret = -EINVAL;
- goto out;
- }
vcpu->run->s.regs.fpc = fpu->fpc;
if (MACHINE_HAS_VX)
convert_fp_to_vx((__vector128 *) vcpu->run->s.regs.vrs,
@@ -4318,7 +4314,6 @@ int kvm_arch_vcpu_ioctl_set_fpu(struct kvm_vcpu *vcpu, struct kvm_fpu *fpu)
else
memcpy(vcpu->run->s.regs.fprs, &fpu->fprs, sizeof(fpu->fprs));
-out:
vcpu_put(vcpu);
return ret;
}
--
2.43.0
next prev parent reply other threads:[~2024-01-16 1:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 1:04 [PATCH AUTOSEL 6.6 01/19] s390/boot: always align vmalloc area on segment boundary Sasha Levin
2024-01-16 1:04 ` [PATCH AUTOSEL 6.6 02/19] arch: consolidate arch_irq_work_raise prototypes Sasha Levin
2024-01-16 1:04 ` [PATCH AUTOSEL 6.6 03/19] s390/vfio-ap: fix sysfs status attribute for AP queue devices Sasha Levin
2024-01-16 1:04 ` [PATCH AUTOSEL 6.6 04/19] Hexagon: Make pfn accessors statics inlines Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 05/19] s390/ptrace: handle setting of fpc register correctly Sasha Levin
2024-01-16 1:05 ` Sasha Levin [this message]
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 07/19] arm64: Fix circular header dependency Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 08/19] sysctl: Fix out of bounds access for empty sysctl registers Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 09/19] SUNRPC: Fix a suspicious RCU usage warning Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 10/19] ext4: enable dioread_nolock as default for bs < ps case Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 11/19] ext4: treat end of range as exclusive in ext4_zero_range() Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 12/19] smb: client: Fix minor whitespace errors and warnings Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 13/19] smb: client: fix renaming of reparse points Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 14/19] smb: client: fix hardlinking " Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 15/19] ecryptfs: Reject casefold directory inodes Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 16/19] ext4: fix inconsistent between segment fstrim and full fstrim Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 17/19] ext4: unify the type of flexbg_size to unsigned int Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 18/19] ext4: remove unnecessary check from alloc_flex_gd() Sasha Levin
2024-01-16 1:05 ` [PATCH AUTOSEL 6.6 19/19] ext4: avoid online resizing failures due to oversized flex bg Sasha Levin
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=20240116010532.218428-6-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=stable@vger.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