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>,
	qemu-stable@nongnu.org
Subject: [PATCH v3 8/9] s390x/css: Use datastream pointer for checking no-data CCWs
Date: Tue, 22 Sep 2026 22:15:24 +0200	[thread overview]
Message-ID: <20260922201526.2383047-9-farman@linux.ibm.com> (raw)
In-Reply-To: <20260922201526.2383047-1-farman@linux.ibm.com>

The channel subsystem will reject channel programs that incorporate
256 CCWs without a data transfer, but the existing check to account
for this only does so for CCWs with a data address of zero. Other
valid CCWs that wouldn't transfer data are not accounted for.

Rather than re-inventing the wheel, use the output of the datastream
at the end of the entire CCW parsing tree to indicate whether data
was moved or not.

Cc: qemu-stable@nongnu.org
Fixes: e8601dd5d0 ("s390x/css: catch ccw sequence errors")
Signed-off-by: Eric Farman <farman@linux.ibm.com>
---
 hw/s390x/css.c | 21 ++++++++++++++-------
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/hw/s390x/css.c b/hw/s390x/css.c
index 9da9128d88..65341c68c3 100644
--- a/hw/s390x/css.c
+++ b/hw/s390x/css.c
@@ -1016,13 +1016,6 @@ static int css_interpret_ccw(SubchDev *sch, hwaddr ccw_addr,
 
     check_len = !((ccw.flags & CCW_FLAG_SLI) && !(ccw.flags & CCW_FLAG_DC));
 
-    if (!ccw.cda) {
-        if (sch->ccw_no_data_cnt == 255) {
-            return -EINVAL;
-        }
-        sch->ccw_no_data_cnt++;
-    }
-
     /* Look at the command. */
     ccw_dstream_init(&sch->cds, &ccw, &(sch->orb));
     switch (ccw.cmd_code) {
@@ -1103,6 +1096,20 @@ static int css_interpret_ccw(SubchDev *sch, hwaddr ccw_addr,
     }
     sch->last_cmd = ccw;
     sch->last_cmd_valid = true;
+
+    /*
+     * A CCW that transfers no data is allowed, but ensure an upper limit
+     * is established to prevent long-running channel programs that don't
+     * move actual data.
+     */
+    if (ret == 0 && sch->cds.at_byte == 0) {
+        if (sch->ccw_no_data_cnt == 255) {
+            ret = -EINVAL;
+        } else {
+            sch->ccw_no_data_cnt++;
+        }
+    }
+
     if (ret == 0) {
         if (ccw.flags & CCW_FLAG_CC) {
             sch->channel_prog += 8;
-- 
2.53.0



  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 ` [PATCH v3 2/9] virtio-ccw: Do not overwrite existing indicators Eric Farman
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 ` Eric Farman [this message]
2026-09-23  1:23   ` [PATCH v3 8/9] s390x/css: Use datastream pointer for checking no-data CCWs 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-9-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.