From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, frankja@linux.ibm.com, david@kernel.org,
seiden@linux.ibm.com, nrb@linux.ibm.com,
schlameuss@linux.ibm.com, gra@linux.ibm.com
Subject: [PATCH v3 0/8] KVM: s390: Even more misc fixes
Date: Fri, 28 Aug 2026 13:54:31 +0200 [thread overview]
Message-ID: <20260828115439.145885-1-imbrenda@linux.ibm.com> (raw)
A few fixes that had been dropped from previous series due to still
having issues, plus a few new fixes.
v2->v3:
* Rebase on master
* Reworked first patch to use scoped_guard() more, and restrict the
scope of the srcu so that it excludes the page pinning
* Add missing const to parameter "old" of kvm_s390_update_cmma_dirty()
* Fix potential infinite loop in dat_get_storage_key() and
dat_reset_reference_bit()
* Fix potential race in _destroy_pages_crste()
v1->v2:
* Fix racy usage of sg->parent in patch 2
* Fix wrong number of arguments for dat_delete_slot() in patch 3
* Restrict srcu usage to the bare minimum necessary to avoid potentially
triggering page faults in the guest while holding the srcu
* Fix races also in other skey functions
Claudio Imbrenda (8):
KVM: s390: Fix dirty marking in adapter_indicators_set*()
KVM: s390: Fix compile warning for kvm_s390_update_cmma_dirty()
KVM: s390: Fix _gaccess_shadow_fault()
KVM: s390: Refactor dat_set_slot()
KVM: s390: Move all code into s390_kvm_mmu_prepare_memory_region()
KVM: s390: Add missing srcu in kvm_s390_set_irq_state()
KVM: s390: Fix potential races in dat skey functions
KVM: s390: Fix race in _destroy_pages_crste()
arch/s390/kvm/gmap/dat.c | 65 +++++++++++++-----------
arch/s390/kvm/gmap/dat.h | 10 ++--
arch/s390/kvm/gmap/gmap.c | 6 ++-
arch/s390/kvm/gmap/kvm_mmu.c | 91 ++++++++++++++--------------------
arch/s390/kvm/gmap/kvm_mmu.h | 4 --
arch/s390/kvm/s390/gaccess.c | 13 +++++
arch/s390/kvm/s390/interrupt.c | 79 ++++++++++++++---------------
arch/s390/kvm/s390/s390.c | 3 +-
arch/s390/kvm/s390/s390.h | 2 +-
9 files changed, 137 insertions(+), 136 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-28 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 11:54 Claudio Imbrenda [this message]
2026-08-28 11:54 ` [PATCH v3 1/8] KVM: s390: Fix dirty marking in adapter_indicators_set*() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 2/8] KVM: s390: Fix compile warning for kvm_s390_update_cmma_dirty() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 3/8] KVM: s390: Fix _gaccess_shadow_fault() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 4/8] KVM: s390: Refactor dat_set_slot() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 5/8] KVM: s390: Move all code into s390_kvm_mmu_prepare_memory_region() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 6/8] KVM: s390: Add missing srcu in kvm_s390_set_irq_state() Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 7/8] KVM: s390: Fix potential races in dat skey functions Claudio Imbrenda
2026-08-28 11:54 ` [PATCH v3 8/8] KVM: s390: Fix race in _destroy_pages_crste() Claudio Imbrenda
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=20260828115439.145885-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gra@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=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®