diff options
author | Claudio Imbrenda <imbrenda@linux.ibm.com> | 2024-12-10 09:39:48 +0100 |
---|---|---|
committer | Claudio Imbrenda <imbrenda@linux.ibm.com> | 2025-01-07 16:36:10 +0100 |
commit | 984aaf6161bcbec22795a61b92f627051a91b465 (patch) | |
tree | 7c1e5dbe4e562e5d7a3efbb2a6bdbde6ddc31bc9 /Documentation | |
parent | Linux 6.13-rc6 (diff) | |
download | linux-984aaf6161bcbec22795a61b92f627051a91b465.tar.xz linux-984aaf6161bcbec22795a61b92f627051a91b465.zip |
KVM: s390: vsie: fix virtual/physical address in unpin_scb()
In commit 77b533411595 ("KVM: s390: VSIE: sort out virtual/physical
address in pin_guest_page"), only pin_scb() has been updated. This
means that in unpin_scb() a virtual address was still used directly as
physical address without conversion. The resulting physical address is
obviously wrong and most of the time also invalid.
Since commit d0ef8d9fbebe ("KVM: s390: Use kvm_release_page_dirty() to
unpin "struct page" memory"), unpin_guest_page() will directly use
kvm_release_page_dirty(), instead of kvm_release_pfn_dirty(), which has
since been removed.
One of the checks that were performed by kvm_release_pfn_dirty() was to
verify whether the page was valid at all, and silently return
successfully without doing anything if the page was invalid.
When kvm_release_pfn_dirty() was still used, the invalid page was thus
silently ignored. Now the check is gone and the result is an Oops.
This also means that when running with a V!=R kernel, the page was not
released, causing a leak.
The solution is simply to add the missing virt_to_phys().
Fixes: 77b533411595 ("KVM: s390: VSIE: sort out virtual/physical address in pin_guest_page")
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Nico Boehr <nrb@linux.ibm.com>
Link: https://lore.kernel.org/r/20241210083948.23963-1-imbrenda@linux.ibm.com
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Message-ID: <20241210083948.23963-1-imbrenda@linux.ibm.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions