All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Farman <farman@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>,
	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,
	qemu-stable@nongnu.org
Subject: Re: [PATCH v3 9/9] s390x/sclp: Reject short headers in PV case
Date: Fri, 25 Sep 2026 07:52:40 -0400	[thread overview]
Message-ID: <3b1ab249-2226-4cbe-b333-a681eeccc12e@linux.ibm.com> (raw)
In-Reply-To: <dbb9db92-6504-4ca3-8ab3-96140a1bf0f8@linux.ibm.com>



On 9/25/26 3:58 AM, Janosch Frank wrote:
> On 9/24/26 4:39 PM, Christian Borntraeger wrote:
>>
>>
>> Am 24.09.26 um 16:36 schrieb Janosch Frank:
>>> On 9/22/26 10:15 PM, Eric Farman wrote:
>>>> An invalid length in an SCCB header correctly generates a specification
>>>> exception for the regular (non-PV) codepath that processes an SCLP
>>>> instruction intercept. The PV case doesn't, even though such a thing
>>>> should already be sanitized. Since a short length will cause problems
> 
> ...even though such a thing should already be handled by the UV.
> 
>>>> later down the line with the storage that will be allocated based on
>>>> that size, put up a defensive check and return if it is too short.
>>>>
>>>> Cc: Janosch Frank <frankja@linux.ibm.com>
>>>> Cc: qemu-stable@nongnu.org
>>>> Fixes: c1db53a591 ("s390/sclp: read sccb from mem based on provided 
>>>> length")
>>>> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
>>>> Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>>>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>>>> ---
>>>
>>> How would you hit that if the architecture says FW will automatically 
>>> inject a spec exception without exiting to the hypervisor if length < 8?
>>
>> As I said in my review, current UV will sanitize this, so this is just 
>> defence in depth in case
>> there would be an implementation error.
> 
> That got lost in my mailbox overflow.
> 
> Alright, then let's extend the comment and commit description before 
> someone deletes this as dead code.

Works for me. I'll fold the above/below comments in when I apply.

> 
>>
>>>
>>> Did you witness this happening?
>>> Am I missing something?
>>>
>>>>    hw/s390x/sclp.c | 6 ++++++
>>>>    1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.c
>>>> index d8b655efcc..ad8129a5d8 100644
>>>> --- a/hw/s390x/sclp.c
>>>> +++ b/hw/s390x/sclp.c
>>>> @@ -277,6 +277,11 @@ int sclp_service_call_protected(S390CPU *cpu, 
>>>> uint64_t sccb, uint32_t code)
>>>>        s390_cpu_pv_mem_read(env_archcpu(env), 0, &header, 
>>>> sizeof(SCCBHeader));
>>>> +    /* Do nothing if the header appears malformed */
> 
> ... We should never end up here due to UV checks but let's be sure.
> 
>>>> +    if (be16_to_cpu(header.length) < sizeof(SCCBHeader)) {
>>>> +        goto out_no_write;
>>>> +    }
>>>> +
>>>>        work_sccb = g_malloc0(be16_to_cpu(header.length));
>>>>        s390_cpu_pv_mem_read(env_archcpu(env), 0, work_sccb,
>>>>                             be16_to_cpu(header.length));
>>>> @@ -290,6 +295,7 @@ int sclp_service_call_protected(S390CPU *cpu, 
>>>> uint64_t sccb, uint32_t code)
>>>>    out_write:
>>>>        s390_cpu_pv_mem_write(env_archcpu(env), 0, work_sccb,
>>>>                              be16_to_cpu(header.length));
>>>> +out_no_write:
>>>>        sclp_c->service_interrupt(sclp, SCLP_PV_DUMMY_ADDR);
>>>>        return 0;
>>>>    }
>>>
>>
> 



  reply	other threads:[~2026-09-25 11:53 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 ` [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 [this message]
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=3b1ab249-2226-4cbe-b333-a681eeccc12e@linux.ibm.com \
    --to=farman@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=frankja@linux.ibm.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.