public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	borntraeger@de.ibm.com, nrb@linux.ibm.com
Subject: Re: [PATCH v1 1/1] KVM: s390: VSIE: fix virtual/physical address in unpin_scb()
Date: Tue, 10 Dec 2024 12:39:39 +0100	[thread overview]
Message-ID: <1dfd5850-3fd0-4b85-8293-ba4221a5e6ae@linux.ibm.com> (raw)
In-Reply-To: <20241210083948.23963-1-imbrenda@linux.ibm.com>

On 12/10/24 9:39 AM, Claudio Imbrenda wrote:
> 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()

Please lower-case the "VSIE" in the subject.
I know that you're replicating the subject prefix from the patch you're 
fixing but this looks weird.

Thanks for fixing this so quickly.
Please push this for CI coverage if you haven't already.

Reviewed-by: Janosch Frank <frankja@linux.ibm.com>

  reply	other threads:[~2024-12-10 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  8:39 [PATCH v1 1/1] KVM: s390: VSIE: fix virtual/physical address in unpin_scb() Claudio Imbrenda
2024-12-10 11:39 ` Janosch Frank [this message]
2024-12-10 12:38 ` Nico Boehr

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=1dfd5850-3fd0-4b85-8293-ba4221a5e6ae@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.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=nrb@linux.ibm.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