From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org
Cc: mjrosato@linux.ibm.com, farman@linux.ibm.com
Subject: Re: [PATCH v4 0/6] KVM s390x PCI fixes
Date: Thu, 23 Jul 2026 14:59:01 +0200 [thread overview]
Message-ID: <6cefe506-b36c-472a-8ab7-ca2483dcc0a9@linux.ibm.com> (raw)
In-Reply-To: <20260722170621.1686-1-alifm@linux.ibm.com>
Am 22.07.26 um 19:06 schrieb Farhan Ali:
> Hi,
>
> This series attempts to fix some the pre-existing issues[1] found by sashiko.
>
> [1] https://lore.kernel.org/all/20260624063447.85DF51F000E9@smtp.kernel.org/
>
> Thanks
> Farhan
>
> ChangeLog
> ---------
> v3: https://lore.kernel.org/all/20260720175819.1723-1-alifm@linux.ibm.com/
> v3 -> v4
> - Add validation checks for AISB/AIBV spanning more than a page.
> - Reject multiple ioctl call for the same device, if adapter interrupt
> forwarding is already enabled for the device.
> - Rebase on 7.2-rc4.
>
> v2: https://lore.kernel.org/all/20260716175241.1039-1-alifm@linux.ibm.com/
> v2 -> v3
> - Remove overwriting guest FIB since we don't use it for
> re-issue (patch 4).
>
> v1: https://lore.kernel.org/all/20260713172600.1284-1-alifm@linux.ibm.com/
> v1 -> v2
> - Drop fix handling AISB/AIBV spanning multiple pages.
> - Fix memory accounting functions for the case when interrupt forwarding
> is enabled by one process but disabled by a different process (patch 1).
>
>
> Farhan Ali (6):
> KVM: s390: pci: Reject adapter interrupt forwarding if already enabled
> KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
> KVM: s390: pci: Fix missing error codes and memory unaccounting
> KVM: s390: pci: Fix NULL dereference on AIBV allocation failure
> KVM: s390: pci: Fix resource leak on IRQ registration failure
> KVM: s390: pci: Validate AIBV and AISB before pinning guest pages
>
> arch/s390/kvm/pci.c | 102 +++++++++++++++++++++++++++++++++++---------
> arch/s390/kvm/pci.h | 2 +
> 2 files changed, 84 insertions(+), 20 deletions(-)
>
I would take this series and do small fixups where necessary. Just tell
me if the change for patch 6 is fine. Or provide a v5.
I suggest to add cc stable to all patches.
next prev parent reply other threads:[~2026-07-23 12:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 17:06 Farhan Ali
2026-07-22 17:06 ` [PATCH v4 1/6] KVM: s390: pci: Reject adapter interrupt forwarding if already enabled Farhan Ali
2026-07-23 6:57 ` Christian Borntraeger
2026-07-23 14:11 ` Matthew Rosato
2026-07-22 17:06 ` [PATCH v4 2/6] KVM: s390: pci: Fix memory accounting for pinned/unpinned pages Farhan Ali
2026-07-23 12:08 ` Christian Borntraeger
2026-07-23 14:12 ` Matthew Rosato
2026-07-23 17:08 ` Farhan Ali
2026-07-23 17:31 ` Matthew Rosato
2026-07-22 17:06 ` [PATCH v4 3/6] KVM: s390: pci: Fix missing error codes and memory unaccounting Farhan Ali
2026-07-23 7:34 ` Christian Borntraeger
2026-07-23 14:15 ` Matthew Rosato
2026-07-22 17:06 ` [PATCH v4 4/6] KVM: s390: pci: Fix NULL dereference on AIBV allocation failure Farhan Ali
2026-07-23 8:18 ` Christian Borntraeger
2026-07-23 14:20 ` Matthew Rosato
2026-07-22 17:06 ` [PATCH v4 5/6] KVM: s390: pci: Fix resource leak on IRQ registration failure Farhan Ali
2026-07-23 12:17 ` Christian Borntraeger
2026-07-23 15:19 ` Matthew Rosato
2026-07-23 16:55 ` Farhan Ali
2026-07-22 17:06 ` [PATCH v4 6/6] KVM: s390: pci: Validate AIBV and AISB before pinning guest pages Farhan Ali
2026-07-23 12:19 ` Christian Borntraeger
2026-07-23 15:35 ` Matthew Rosato
2026-07-23 12:59 ` Christian Borntraeger [this message]
2026-07-23 13:00 ` [PATCH v4 0/6] KVM s390x PCI fixes Matthew Rosato
2026-07-23 15:35 ` Matthew Rosato
2026-07-23 16:38 ` Farhan Ali
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=6cefe506-b36c-472a-8ab7-ca2483dcc0a9@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@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
Powered by JetHome