From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, borntraeger@de.ibm.com
Subject: [GIT PULL v1 0/1] Subject: [GIT PULL v1 0/1] KVM: s390: One very last second fix
Date: Tue, 7 Apr 2026 18:27:25 +0200 [thread overview]
Message-ID: <20260407162726.252141-1-imbrenda@linux.ibm.com> (raw)
Ciao Paolo,
here is one very last moment fix for the gmap rewrite. It fixes an
issue that can happen when a partial invalidation happens during a
shadowing operation.
The following changes since commit bfe62a454542cfad3379f6ef5680b125f41e20f4:
Merge tag 'soc-fixes-7.0-2' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc (2026-04-06 09:03:19 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-7.0-4
for you to fetch changes up to 3ffe5eb4a5f248c0d4b849f050af973396656f85:
KVM: s390: vsie: Fix races with partial gmap invalidations (2026-04-07 18:20:58 +0200)
----------------------------------------------------------------
KVM: s390: One very last second fix
Fix one more gmap-rewrite issue: races with partial gmap invalidations.
----------------------------------------------------------------
Claudio Imbrenda (1):
KVM: s390: vsie: Fix races with partial gmap invalidations
arch/s390/kvm/gaccess.c | 9 +++++----
arch/s390/kvm/gmap.c | 3 +++
arch/s390/kvm/gmap.h | 1 +
3 files changed, 9 insertions(+), 4 deletions(-)
next reply other threads:[~2026-04-07 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 16:27 Claudio Imbrenda [this message]
2026-04-07 16:27 ` [GIT PULL v1 1/1] KVM: s390: vsie: Fix races with partial gmap invalidations Claudio Imbrenda
2026-04-11 12:09 ` [GIT PULL v1 0/1] Subject: [GIT PULL v1 0/1] KVM: s390: One very last second fix Paolo Bonzini
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=20260407162726.252141-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.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