From: Farhan Ali <alifm@linux.ibm.com>
To: stable@vger.kernel.org, gregkh@linuxfoundation.org, sashal@kernel.org
Cc: alifm@linux.ibm.com
Subject: [PATCH v3 stable 6.1 0/5] s390 KVM PCI backports for 6.1
Date: Mon, 17 Aug 2026 13:16:01 -0700 [thread overview]
Message-ID: <20260817201606.3194-1-alifm@linux.ibm.com> (raw)
Hi,
This patchset backports the s390 KVM PCI fixes to stable-6.1. The patchset
includes one dependency patch (patch 1) from Jason Gunthorpe, to export
free_uid(). This is needed to resolve a compilation error. I have resolved
all other merge conflicts and tested them on s390.
Thanks
Farhan
Farhan Ali (3):
KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
KVM: s390: pci: Fix missing error codes and memory unaccounting
KVM: s390: pci: Fix resource leak on IRQ registration failure
Jason Gunthorpe (1):
kernel/user: Allow user_struct::locked_vm to be usable for iommufd
Matthew Rosato (1):
KVM: s390: pci: Fix aisb calculation
arch/s390/kvm/pci.c | 86 +++++++++++++++++++++++++++-----------
arch/s390/kvm/pci.h | 2 +
include/linux/sched/user.h | 2 +-
kernel/user.c | 1 +
4 files changed, 66 insertions(+), 25 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-17 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 20:16 Farhan Ali [this message]
2026-08-17 20:16 ` [PATCH v3 1/5] kernel/user: Allow user_struct::locked_vm to be usable for iommufd Farhan Ali
2026-08-17 21:24 ` Bradley Morgan
2026-08-17 21:33 ` Bradley Morgan
2026-08-17 20:16 ` [PATCH v3 2/5] KVM: s390: pci: Fix memory accounting for pinned/unpinned pages Farhan Ali
2026-08-17 20:16 ` [PATCH v3 3/5] KVM: s390: pci: Fix missing error codes and memory unaccounting Farhan Ali
2026-08-17 20:16 ` [PATCH v3 4/5] KVM: s390: pci: Fix resource leak on IRQ registration failure Farhan Ali
2026-08-17 20:16 ` [PATCH v3 5/5] KVM: s390: pci: Fix aisb calculation Farhan Ali
2026-08-19 3:32 ` [PATCH v3 stable 6.1 0/5] s390 KVM PCI backports for 6.1 Sasha Levin
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=20260817201606.3194-1-alifm@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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