All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Farman <farman@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	Eric Farman <farman@linux.ibm.com>,
	Anthony Krowiak <akrowiak@linux.ibm.com>,
	qemu-stable@nongnu.org
Subject: [PATCH 4/9] vfio/ap: Clear error object pointer after non-fatal errors
Date: Wed, 16 Sep 2026 22:32:36 +0200	[thread overview]
Message-ID: <20260916203242.2509787-5-farman@linux.ibm.com> (raw)
In-Reply-To: <20260916203242.2509787-1-farman@linux.ibm.com>

Registering a new IRQ notifier will allocate an error object if needed,
and warn_report_err() will release that memory once it's finished.
The pointer remains, however, so subsequent errors after the non-fatal
errors in vfio_ap_realize() would cause an assertion failure for a
non-NULL pointer.

Fix this by clearing the pointer once the warning has been reported,
to reset the state of the error objects.

Cc: Anthony Krowiak <akrowiak@linux.ibm.com>
Cc: qemu-stable@nongnu.org
Fixes: 1360b2ad1f ("s390x/ap: Wire up the device request notifier interface")
Fixes: 0fb8a62fe4 ("hw/vfio/ap: notification handler for AP config changed event")
Signed-off-by: Eric Farman <farman@linux.ibm.com>
---
 hw/vfio/ap.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
index 6e2a1223ea..2926e04ad4 100644
--- a/hw/vfio/ap.c
+++ b/hw/vfio/ap.c
@@ -247,8 +247,10 @@ static void vfio_ap_realize(DeviceState *dev, Error **errp)
         /*
          * Report this error, but do not make it a failing condition.
          * Lack of this IRQ in the host does not prevent normal operation.
+         * Clear the pointer, since the warning will release it.
          */
         warn_report_err(err);
+        err = NULL;
     }
 
     if (!vfio_ap_register_irq_notifier(vapdev, VFIO_AP_CFG_CHG_IRQ_INDEX, &err))
@@ -256,8 +258,10 @@ static void vfio_ap_realize(DeviceState *dev, Error **errp)
         /*
          * Report this error, but do not make it a failing condition.
          * Lack of this IRQ in the host does not prevent normal operation.
+         * Clear the pointer, since the warning will release it.
          */
         warn_report_err(err);
+        err = NULL;
     }
 
     return;
-- 
2.53.0



  parent reply	other threads:[~2026-09-16 20:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 20:32 [PATCH 0/9] s390x: even more hardening fixes Eric Farman
2026-09-16 20:32 ` [PATCH 1/9] virtio-ccw: Limit ISC to MAX_ISC Eric Farman
2026-09-16 23:15   ` Matthew Rosato
2026-09-17  7:36     ` Christian Borntraeger
2026-09-17 12:09     ` Eric Farman
2026-09-21 15:02       ` Eric Farman
2026-09-16 20:32 ` [PATCH 2/9] virtio-ccw: Do not overwrite existing indicators Eric Farman
2026-09-16 23:15   ` Matthew Rosato
2026-09-17  7:35   ` Christian Borntraeger
2026-09-17 16:17     ` Eric Farman
2026-09-16 20:32 ` [PATCH 3/9] virtio-ccw: Fix rc check in read configuration path Eric Farman
2026-09-16 23:15   ` Matthew Rosato
2026-09-16 20:32 ` Eric Farman [this message]
2026-09-16 23:15   ` [PATCH 4/9] vfio/ap: Clear error object pointer after non-fatal errors Matthew Rosato
2026-09-17 12:50   ` Anthony Krowiak
2026-09-16 20:32 ` [PATCH 5/9] vfio/ccw: " Eric Farman
2026-09-16 23:15   ` Matthew Rosato
2026-09-17 12:23     ` Eric Farman
2026-09-16 20:32 ` [PATCH 6/9] hw/intc/s390x: Fix payload to KVM_HAS_DEVICE_ATTR ioctl Eric Farman
2026-09-16 23:15   ` Matthew Rosato
2026-09-17  7:45   ` Christian Borntraeger
2026-09-17 12:15     ` Eric Farman
2026-09-17 12:25       ` Christian Borntraeger
2026-09-16 20:32 ` [PATCH 7/9] hw/intc/s390x: Fix check after g_try_realloc Eric Farman
2026-09-16 23:16   ` Matthew Rosato
2026-09-17 12:57     ` Eric Farman
2026-09-16 20:32 ` [PATCH 8/9] s390x/css: Expand check against no-data-count CCWs Eric Farman
2026-09-16 23:16   ` Matthew Rosato
2026-09-17 15:55     ` Eric Farman
2026-09-16 20:32 ` [PATCH 9/9] s390x/sclp: Reject short headers in PV case Eric Farman
2026-09-16 23:16   ` Matthew Rosato
2026-09-17  7:53   ` Christian Borntraeger

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=20260916203242.2509787-5-farman@linux.ibm.com \
    --to=farman@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=qemu-stable@nongnu.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 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.