From: David Hildenbrand <david@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, frankja@linux.ibm.com,
borntraeger@de.ibm.com, nrb@linux.ibm.com, seiden@linux.ibm.com,
nsg@linux.ibm.com, schlameuss@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH v3 1/1] KVM: s390: pv: fix race when making a page secure
Date: Tue, 4 Mar 2025 10:45:40 +0100 [thread overview]
Message-ID: <9f4d8c72-7bd9-4388-9442-3c84cd0a4558@redhat.com> (raw)
In-Reply-To: <20250304102134.1bd9fb03@p-imbrenda>
On 04.03.25 10:21, Claudio Imbrenda wrote:
> On Fri, 28 Feb 2025 22:15:04 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>> On 27.02.25 14:09, Claudio Imbrenda wrote:
>>> Holding the pte lock for the page that is being converted to secure is
>>> needed to avoid races. A previous commit removed the locking, which
>>> caused issues. Fix by locking the pte again.
>>>
>>> Fixes: 5cbe24350b7d ("KVM: s390: move pv gmap functions into kvm")
>>> Reported-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
>>
>> Tested with shmem / memory-backend-memfd that ends up using large folios
>> / THPs.
>>
>> Tested-by: David Hildenbrand <david@redhat.com>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>>
>> Two comments below.
>
> I will need to send a v4, unfortunately there are other issues with this
> patch (as you have probably noticed by now as well)
I ran into some weird KVM_PV_VERIFY issues a couple of times, but did
not find the root cause so far.
Is that what you are seeing? (and what is the root cause? :) )
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-03-04 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 13:09 [PATCH v3 0/1] KVM: s390: fix a newly introduced bug Claudio Imbrenda
2025-02-27 13:09 ` [PATCH v3 1/1] KVM: s390: pv: fix race when making a page secure Claudio Imbrenda
2025-02-28 21:15 ` David Hildenbrand
2025-03-04 9:21 ` Claudio Imbrenda
2025-03-04 9:45 ` David Hildenbrand [this message]
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=9f4d8c72-7bd9-4388-9442-3c84cd0a4558@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@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=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=schlameuss@linux.ibm.com \
--cc=seiden@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