All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Zhuoying Cai <zycai@linux.ibm.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: jrossi@linux.ibm.com, berrange@redhat.com,
	richard.henderson@linaro.org, david@kernel.org,
	walling@linux.ibm.com, jjherne@linux.ibm.com,
	pasic@linux.ibm.com, borntraeger@linux.ibm.com,
	farman@linux.ibm.com, mjrosato@linux.ibm.com, iii@linux.ibm.com,
	eblake@redhat.com, armbru@redhat.com, zycai@linux.ibm.com,
	alifm@linux.ibm.com, brueckner@linux.ibm.com,
	pierrick.bouvier@oss.qualcomm.com, jdaley@linux.ibm.com
Subject: Re: [PATCH v15 14/33] s390x/diag: Implement DIAG 508 subcode 1 for signature verification
Date: Tue, 07 Jul 2026 11:44:11 +0200	[thread overview]
Message-ID: <87h5mbjfro.fsf@redhat.com> (raw)
In-Reply-To: <20260704213950.2118823-15-zycai@linux.ibm.com>

On Sat, Jul 04 2026, Zhuoying Cai <zycai@linux.ibm.com> wrote:

> From: Collin Walling <walling@linux.ibm.com>
>
> DIAG 508 subcode 1 performs signature-verification on signed components.
> A signed component may be a Linux kernel image, or any other signed
> binary. **Verification of initrd is not supported.**
>
> The instruction call expects two item-pairs: an address of a device
> component, an address of the analogous signature file (in PKCS#7 DER format),
> and their respective lengths. All of this data should be encapsulated
> within a Diag508SigVerifBlock.
>
> The DIAG handler will read from the provided addresses
> to retrieve the necessary data, parse the signature file, then
> perform the signature-verification. Because there is no way to
> correlate a specific certificate to a component, each certificate
> in the store is tried until either verification succeeds, or all
> certs have been exhausted.
>
> A return code of 1 indicates success, and the index and length of the
> corresponding certificate will be set in the Diag508SigVerifBlock.
> The following values indicate failure:
>
> 	0x0102: no certificates are available in the store
> 	0x0202: component data is invalid
> 	0x0302: PKCS#7 format signature is invalid
> 	0x0402: signature-verification failed
> 	0x0502: length of Diag508SigVerifBlock is invalid
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> Signed-off-by: Zhuoying Cai <zycai@linux.ibm.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Reviewed-by: Farhan Ali<alifm@linux.ibm.com>
> ---
>  docs/specs/s390x-secure-ipl.rst |  17 +++++
>  include/hw/s390x/ipl/diag508.h  |  30 +++++++++
>  target/s390x/diag.c             | 111 +++++++++++++++++++++++++++++++-
>  3 files changed, 157 insertions(+), 1 deletion(-)

(...)

> +    if (!comp_len || !comp_addr || comp_len > DIAG_508_MAX_COMP_LEN) {
> +        if (comp_len > DIAG_508_MAX_COMP_LEN) {
> +            warn_report("DIAG 0x508: component length %lu exceeds current maximum %u",
> +                        comp_len, DIAG_508_MAX_COMP_LEN);
> +        }
> +        return DIAG_508_RC_INVAL_COMP_DATA;
> +    }
> +
> +    if (!sig_len || !sig_addr || sig_len > DIAG_508_MAX_SIG_LEN) {
> +        if (sig_len > DIAG_508_MAX_SIG_LEN) {
> +            warn_report("DIAG 0x508: signature length %lu exceeds current maximum %u",
> +                        sig_len, DIAG_508_MAX_SIG_LEN);
> +        }
> +        return DIAG_508_RC_INVAL_PKCS7_SIG;
> +    }

Hi,

I'm afraid this breaks the build on win64 (as done by the ci):

../target/s390x/diag.c: In function 'handle_diag508_sig_verif':
../target/s390x/diag.c:683:57: error: format '%lu' expects argument of type 'long unsigned int', but argument 2 has type 'uint64_t' {aka 'long long unsigned int'} [-Werror=format=]
  683 |             warn_report("DIAG 0x508: component length %lu exceeds current maximum %u",
      |                                                       ~~^
      |                                                         |
      |                                                         long unsigned int
      |                                                       %llu
  684 |                         comp_len, DIAG_508_MAX_COMP_LEN);
      |                         ~~~~~~~~
      |                         |
      |                         uint64_t {aka long long unsigned int}
../target/s390x/diag.c:691:57: error: format '%lu' expects argument of type 'long unsigned int', but argument 2 has type 'uint64_t' {aka 'long long unsigned int'} [-Werror=format=]
  691 |             warn_report("DIAG 0x508: signature length %lu exceeds current maximum %u",
      |                                                       ~~^
      |                                                         |
      |                                                         long unsigned int
      |                                                       %llu
  692 |                         sig_len, DIAG_508_MAX_SIG_LEN);
      |                         ~~~~~~~
      |                         |
      |                         uint64_t {aka long long unsigned int}

Cornelia



  reply	other threads:[~2026-07-07  9:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 21:39 [PATCH v15 00/33] Secure IPL Support for SCSI Scheme of virtio-blk/virtio-scsi Devices Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 01/33] Add boot-certs to s390-ccw-virtio machine type option Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 02/33] crypto/x509-utils: Refactor with GNUTLS fallback Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 03/33] crypto/x509-utils: Add helper functions for certificate store Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 04/33] hw/s390x/ipl: Create " Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 05/33] s390x/diag: Introduce DIAG 320 for Certificate Store Facility Zhuoying Cai
2026-07-07  9:51   ` Cornelia Huck
2026-07-04 21:39 ` [PATCH v15 06/33] s390x/diag: Refactor address validation check from diag308_parm_check Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 07/33] s390x/diag: Implement DIAG 320 subcode 1 Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 08/33] crypto/x509-utils: Add helper functions for DIAG 320 subcode 2 Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 09/33] s390x/diag: Implement " Zhuoying Cai
2026-07-05 22:42   ` Jared Rossi
2026-07-04 21:39 ` [PATCH v15 10/33] hw/s390x: Define finite size for single entry VCEntry Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 11/33] s390x/diag: Introduce DIAG 508 for secure IPL operations Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 12/33] crypto/x509-utils: Add helper functions for DIAG 508 subcode 1 Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 13/33] s390x/diag: Generalize s390_ipl_read/write to accept void * Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 14/33] s390x/diag: Implement DIAG 508 subcode 1 for signature verification Zhuoying Cai
2026-07-07  9:44   ` Cornelia Huck [this message]
2026-07-04 21:39 ` [PATCH v15 15/33] s390x/ipl: Introduce IPL Information Report Block (IIRB) Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 16/33] pc-bios/s390-ccw: Define memory for IPLB and convert IPLB to pointers Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 17/33] hw/s390x/ipl: Add IPIB flags to IPL Parameter Block Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 18/33] hw/s390x/ipl: Rework s390_ipl_map_iplb_chain for certificate storage Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 19/33] s390x: Guest support for Secure-IPL Facility Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 20/33] pc-bios/s390-ccw: Refactor zipl_run() Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 21/33] pc-bios/s390-ccw: Rework zipl_load_segment function Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 22/33] pc-bios/s390-ccw: Introduce ZiplBootMode enum for IPL mode selection Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 23/33] pc-bios/s390-ccw: Add signature verification for secure IPL in audit mode Zhuoying Cai
2026-07-05 22:43   ` Jared Rossi
2026-07-04 21:39 ` [PATCH v15 24/33] pc-bios/s390-ccw: Add signed component address overlap checks Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 25/33] s390x: Guest support for Secure-IPL Code Loading Attributes Facility (SCLAF) Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 26/33] pc-bios/s390-ccw: Add additional security checks for secure boot Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 27/33] Add secure-boot to s390-ccw-virtio machine type option Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 28/33] hw/s390x/ipl: Set IPIB flags for secure IPL Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 29/33] pc-bios/s390-ccw: Handle true secure IPL mode Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 30/33] hw/s390x/ipl: Handle secure boot with multiple boot devices Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 31/33] tests/functional/s390x: Add secure IPL functional test Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 32/33] docs/specs: Add secure IPL documentation Zhuoying Cai
2026-07-04 21:39 ` [PATCH v15 33/33] docs/system/s390x: " Zhuoying Cai

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=87h5mbjfro.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=brueckner@linux.ibm.com \
    --cc=david@kernel.org \
    --cc=eblake@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=jdaley@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=jrossi@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=walling@linux.ibm.com \
    --cc=zycai@linux.ibm.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.