From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: jjherne@linux.ibm.com, borntraeger@de.ibm.com,
mjrosato@linux.ibm.com, pasic@linux.ibm.com, alex@shazbot.org,
kwankhede@nvidia.com, fiuczy@linux.ibm.com, pbonzini@redhat.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com,
agordeev@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com
Subject: [PATCH v4 0/4] s390/vfio-ap: Fix pre-existing bugs in vfio_ap device driver
Date: Fri, 28 Aug 2026 17:46:49 -0400 [thread overview]
Message-ID: <20260828214653.1087009-1-akrowiak@linux.ibm.com> (raw)
The sashiko AI reported several pre-existing bugs in the vfio_ap device
driver code while reviewing unrelated patches. This series fixes four
such bugs.
Change log v3 => v4:
~~~~~~~~~~~~~~~~~~~
Patch 1/4: Fix leak of pinned NIB and registered NISC in
vfio_ap_irq_enable/disable()
* Overrode the response status in vfio_irq_disable() for the
AP_RESPONSE_NORMAL case when vfio_ap_wait_for_irqclear() returns false.
* Changed name of vfio_ap_wait_for_irqclear() to
vfio_ap_wait_for_irq_state() and added a parameter to specify
the value (0 = disabled, 1 = enabled) to which the status.irq_enabled
(I-bit) is to be compared.
* Added a call to vfio_ap_wait_for_irq_state() to vfio_ap_irq_enable()
to verify that the I-bit is set when AP_RESPONSE_NORMAL is returned
from the AQIC call before proceeding.
Patch 3/4: Fix unbounded loop in apq_reset_check()
* Check return code from apq_status_check() called from apq_reset_check().
If it returns 0 when the AP_RESET_MAX_WAIT timeout is detected, then
clean up AQIC resources.
Anthony Krowiak (4):
s390/vfio-ap: Fix leak of pinned NIB and registered NISC in
vfio_ap_irq_enable/disable()
s390/vfio-ap: Fix failure to release IRQ notification eventfd contexts
s390/vfio-ap: Fix unbounded loop in apq_reset_check()
s390/vfio-ap: Use AP_DOMAINS for adm_add bitmap size in
vfio_ap_mdev_cfg_add()
drivers/s390/crypto/vfio_ap_ops.c | 216 +++++++++++++++++++++++++-----
1 file changed, 186 insertions(+), 30 deletions(-)
--
2.53.0
next reply other threads:[~2026-08-28 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 21:46 Anthony Krowiak [this message]
2026-08-28 21:46 ` [PATCH v4 1/4] s390/vfio-ap: Fix leak of pinned NIB and registered NISC in vfio_ap_irq_enable/disable() Anthony Krowiak
2026-08-28 21:57 ` sashiko-bot
2026-08-31 10:26 ` Anthony Krowiak
2026-08-31 10:30 ` Anthony Krowiak
2026-08-28 21:46 ` [PATCH v4 2/4] s390/vfio-ap: Fix failure to release IRQ notification eventfd contexts Anthony Krowiak
2026-08-28 21:54 ` sashiko-bot
2026-08-28 21:46 ` [PATCH v4 3/4] s390/vfio-ap: Fix unbounded loop in apq_reset_check() Anthony Krowiak
2026-08-28 22:02 ` sashiko-bot
2026-08-31 12:38 ` Anthony Krowiak
2026-08-28 21:46 ` [PATCH v4 4/4] s390/vfio-ap: Use AP_DOMAINS for adm_add bitmap size in vfio_ap_mdev_cfg_add() Anthony Krowiak
2026-08-28 21:52 ` sashiko-bot
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=20260828214653.1087009-1-akrowiak@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=borntraeger@de.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.