From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, david@redhat.com, frankja@linux.ibm.com,
seiden@linux.ibm.com, nsg@linux.ibm.com, nrb@linux.ibm.com,
schlameuss@linux.ibm.com, hca@linux.ibm.com,
mhartmay@linux.ibm.com
Subject: Re: [PATCH v1 2/2] KVM: s390: Fix FOLL_*/FAULT_FLAG_* confusion
Date: Tue, 5 Aug 2025 13:59:31 +0200 [thread overview]
Message-ID: <20250805135931.0dbcf0f2@p-imbrenda> (raw)
In-Reply-To: <5b0b8d5e-efab-4c5b-be1e-93d8a8f155b3@de.ibm.com>
On Tue, 5 Aug 2025 13:44:04 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Am 05.08.25 um 13:14 schrieb Claudio Imbrenda:
> > Pass the right type of flag to vcpu_dat_fault_handler(); it expects a
> > FOLL_* flag (in particular FOLL_WRITE), but FAULT_FLAG_WRITE is passed
> > instead.
> >
> > This still works because they happen to have the same integer value,
> > but it's a mistake, thus the fix.
> >
> > Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> > Fixes: 05066cafa925 ("s390/mm/fault: Handle guest-related program interrupts in KVM")
>
> Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>
> Shouldnt we rename the parameter to __kvm_s390_handle_dat_fault and
> vcpu_dat_fault_handler from flags to foll as well in their
> implementation and prototypes to keep this consistent?
that's a fair point
a patch in an upcoming series will do that, but I guess I can move that
change here instead.
I'll send a v2 later on today
>
> > ---
> > arch/s390/kvm/kvm-s390.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> > index d5ad10791c25..d41d77f2c7cd 100644
> > --- a/arch/s390/kvm/kvm-s390.c
> > +++ b/arch/s390/kvm/kvm-s390.c
> > @@ -4954,13 +4954,13 @@ static int vcpu_dat_fault_handler(struct kvm_vcpu *vcpu, unsigned long gaddr, un
> >
> > static int vcpu_post_run_handle_fault(struct kvm_vcpu *vcpu)
> > {
> > - unsigned int flags = 0;
> > + unsigned int foll = 0;
> > unsigned long gaddr;
> > int rc;
> >
> > gaddr = current->thread.gmap_teid.addr * PAGE_SIZE;
> > if (kvm_s390_cur_gmap_fault_is_write())
> > - flags = FAULT_FLAG_WRITE;
> > + foll = FOLL_WRITE;
> >
> > switch (current->thread.gmap_int_code & PGM_INT_CODE_MASK) {
> > case 0:
> > @@ -5002,7 +5002,7 @@ static int vcpu_post_run_handle_fault(struct kvm_vcpu *vcpu)
> > send_sig(SIGSEGV, current, 0);
> > if (rc != -ENXIO)
> > break;
> > - flags = FAULT_FLAG_WRITE;
> > + foll = FOLL_WRITE;
> > fallthrough;
> > case PGM_PROTECTION:
> > case PGM_SEGMENT_TRANSLATION:
> > @@ -5012,7 +5012,7 @@ static int vcpu_post_run_handle_fault(struct kvm_vcpu *vcpu)
> > case PGM_REGION_SECOND_TRANS:
> > case PGM_REGION_THIRD_TRANS:
> > kvm_s390_assert_primary_as(vcpu);
> > - return vcpu_dat_fault_handler(vcpu, gaddr, flags);
> > + return vcpu_dat_fault_handler(vcpu, gaddr, foll);
> > default:
> > KVM_BUG(1, vcpu->kvm, "Unexpected program interrupt 0x%x, TEID 0x%016lx",
> > current->thread.gmap_int_code, current->thread.gmap_teid.val);
>
next prev parent reply other threads:[~2025-08-05 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 11:14 [PATCH v1 0/2] KVM: s390: Fix two bugs Claudio Imbrenda
2025-08-05 11:14 ` [PATCH v1 1/2] KVM: s390: Fix incorrect usage of mmu_notifier_register() Claudio Imbrenda
2025-08-05 11:54 ` Christian Borntraeger
2025-08-05 12:09 ` David Hildenbrand
2025-08-05 12:16 ` Steffen Eiden
2025-08-05 13:07 ` Christoph Schlameuss
2025-08-05 11:14 ` [PATCH v1 2/2] KVM: s390: Fix FOLL_*/FAULT_FLAG_* confusion Claudio Imbrenda
2025-08-05 11:44 ` Christian Borntraeger
2025-08-05 11:59 ` Claudio Imbrenda [this message]
2025-08-05 12:11 ` David Hildenbrand
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=20250805135931.0dbcf0f2@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--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
all inboxes | Powered by JetHome®