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>,
qemu-stable@nongnu.org
Subject: [PATCH v3 2/9] virtio-ccw: Do not overwrite existing indicators
Date: Tue, 22 Sep 2026 22:15:18 +0200 [thread overview]
Message-ID: <20260922201526.2383047-3-farman@linux.ibm.com> (raw)
In-Reply-To: <20260922201526.2383047-1-farman@linux.ibm.com>
The various indicators pointers allow them to be overwritten,
but leak any existing structs that might be there. If indicators
exist, ensure that they are released before setting the new ones.
Both the regular and adapter interrupt paths check that they
aren't being asked to enable interrupts when the other one is
enabled, so just do this release once all the potential checks
are completed.
Cc: qemu-stable@nongnu.org
Fixes: 7bca3892cb ("s390x/virtio-ccw: reference-counted indicators")
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Eric Farman <farman@linux.ibm.com>
---
hw/s390x/virtio-ccw.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
index eb6378ea4c..f46f936150 100644
--- a/hw/s390x/virtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -582,6 +582,11 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
if (ret) {
break;
}
+ if (dev->indicators) {
+ /* Need to remove existing indicators first */
+ release_indicator(&dev->routes.adapter, dev->indicators);
+ dev->indicators = NULL;
+ }
indicators = be64_to_cpu(indicators);
dev->indicators = get_indicator(indicators, sizeof(uint64_t));
sch->curr_status.scsw.count = ccw.count - sizeof(indicators);
@@ -606,6 +611,11 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
if (ret) {
break;
}
+ if (dev->indicators2) {
+ /* Need to remove existing indicators first */
+ release_indicator(&dev->routes.adapter, dev->indicators2);
+ dev->indicators2 = NULL;
+ }
indicators = be64_to_cpu(indicators);
dev->indicators2 = get_indicator(indicators, sizeof(uint64_t));
sch->curr_status.scsw.count = ccw.count - sizeof(indicators);
@@ -666,6 +676,17 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
} else if (thinint.isc > MAX_ISC) {
ret = -ENOSYS;
} else {
+ if (dev->indicators) {
+ /* Need to remove existing indicators first */
+ release_indicator(&dev->routes.adapter, dev->indicators);
+ dev->indicators = NULL;
+ }
+ if (dev->summary_indicator) {
+ /* Need to remove existing indicators first */
+ release_indicator(&dev->routes.adapter,
+ dev->summary_indicator);
+ dev->summary_indicator = NULL;
+ }
thinint.ind_bit = be64_to_cpu(thinint.ind_bit);
thinint.summary_indicator =
be64_to_cpu(thinint.summary_indicator);
--
2.53.0
next prev parent reply other threads:[~2026-09-22 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:15 [PATCH v3 0/9] s390x: even more hardening fixes Eric Farman
2026-09-22 20:15 ` [PATCH v3 1/9] virtio-ccw: Limit ISC to MAX_ISC Eric Farman
2026-09-22 20:15 ` Eric Farman [this message]
2026-09-22 20:15 ` [PATCH v3 3/9] virtio-ccw: Fix rc check in read configuration path Eric Farman
2026-09-22 20:15 ` [PATCH v3 4/9] vfio/ap: Clear error object pointer after non-fatal errors Eric Farman
2026-09-22 20:15 ` [PATCH v3 5/9] vfio/ccw: " Eric Farman
2026-09-22 20:15 ` [PATCH v3 6/9] hw/intc/s390x: Fix payload to KVM_HAS_DEVICE_ATTR ioctl Eric Farman
2026-09-22 20:15 ` [PATCH v3 7/9] hw/intc/s390x: Fix check after g_try_realloc Eric Farman
2026-09-22 20:15 ` [PATCH v3 8/9] s390x/css: Use datastream pointer for checking no-data CCWs Eric Farman
2026-09-23 1:23 ` Matthew Rosato
2026-09-22 20:15 ` [PATCH v3 9/9] s390x/sclp: Reject short headers in PV case Eric Farman
2026-09-24 14:36 ` Janosch Frank
2026-09-24 14:39 ` Christian Borntraeger
2026-09-25 7:58 ` Janosch Frank
2026-09-25 11:52 ` Eric Farman
2026-09-23 7:21 ` [PATCH v3 0/9] s390x: even more hardening fixes Christian Borntraeger
2026-09-25 12:54 ` Eric Farman
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=20260922201526.2383047-3-farman@linux.ibm.com \
--to=farman@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.