From: sashiko-bot@kernel.org
To: "Jiri Pirko" <jiri@resnulli.us>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH RFC 07/20] ctlv: Prepare schema validation
Date: Thu, 15 Oct 2026 15:14:37 +0000 [thread overview]
Message-ID: <sashiko-outbox-173043@kernel.org> (raw)
In-Reply-To: <20261015145053.3664509-8-jiri@resnulli.us>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] ctlv: schema traversal ignores stub fills in reentering calculations
--
commit c53ad2ae9e8a16f911d52d764c978f30d89b6d14
Author: Jiri Pirko <jiri@resnulli.us>
ctlv: Prepare schema validation
Add generated-schema walking, message validation and request indexing.
Use the descriptor layer for blob placement checks. Keep CONFIG_CTLV unwired
until dispatch completes the module.
> diff --git a/drivers/ctlv/schema.c b/drivers/ctlv/schema.c
> new file mode 100644
> index 0000000000000..b74f9a358bc34
> --- /dev/null
> +++ b/drivers/ctlv/schema.c
[ ... ]
> +/* Size one deepest legal leaf and every nest above it. */
> +static u64 ctlv_schema_reentering_min_len(struct ctlv_schema_length_walk *walk,
> + const struct ctlv_schema_tree *tree)
> +{
> + u64 leaf = 0;
> + u32 index;
> +
> + for (index = 1; index < tree->node_schemas_count; index++) {
> + if (tree->node_schemas[index].kind == CTLV_SCHEMA_NEST)
> + continue;
> + leaf = max(leaf,
> + ALIGN(ctlv_schema_attr_max_len(walk, tree, index, 0), CTLV_ALIGNTO));
> + }
[Severity: Medium]
Does this calculation miss injected stub schemas? It iterates only over
tree->node_schemas_count, completely ignoring tree->stub_schemas.
This seems like it could miss any large leaves injected by stub fills,
underestimating the query reply buffer size (query_reply_min_len) and
potentially leading to message truncation in userspace.
> + return (CTLV_MAX_NEST_DEPTH + 1) * sizeof(struct ctlv_attr) + leaf;
> +}
> +
> +static bool ctlv_schema_tree_reenters(const struct ctlv_schema_tree *tree)
> +{
> + u32 index;
> +
> + for (index = 0; index < tree->node_schemas_count; index++)
> + if (tree->node_schemas[index].reenters)
> + return true;
[Severity: Medium]
Will this loop return false when reentering nodes are present only inside stub
fills? Because it only checks tree->node_schemas_count, it might cause
ctlv_schema_op_sizes() to incorrectly fall back to ctlv_schema_min_len().
If that fallback occurs, ctlv_schema_min_len() would recursively descend into
the reentering stub fill until its depth exceeds CTLV_MAX_DECLARED_NEST_DEPTH.
At that point, walk->bad becomes true and valid schemas could be incorrectly
rejected with -EINVAL.
> + return false;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261015145053.3664509-1-jiri@resnulli.us?part=7
next prev parent reply other threads:[~2026-10-15 15:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:50 [PATCH RFC 00/20] attestation: Add a common subsystem and TDX support Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 01/20] ctlv: Add the schema language and generator Jiri Pirko
2026-10-15 14:58 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 02/20] ctlv: Add the UAPI wire format and family API Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 03/20] ctlv: Add the root family specification and generated files Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 04/20] Documentation: ctlv: Add userspace ABI Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 05/20] ctlv: Prepare message input handling Jiri Pirko
2026-10-15 15:06 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 06/20] ctlv: Prepare blob descriptor validation Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 07/20] ctlv: Prepare schema validation Jiri Pirko
2026-10-15 15:14 ` sashiko-bot [this message]
2026-10-15 14:50 ` [PATCH RFC 08/20] ctlv: Prepare message output handling Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 09/20] ctlv: Prepare VA blob handling Jiri Pirko
2026-10-15 15:14 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 10/20] ctlv: Prepare event queue support Jiri Pirko
2026-10-15 15:22 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 11/20] ctlv: Prepare runtime introspection Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 12/20] ctlv: Add device and operation dispatch Jiri Pirko
2026-10-15 15:28 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 13/20] Documentation: ctlv: Describe how to write a family Jiri Pirko
2026-10-15 15:20 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 14/20] attestation: Add the base family specification and generated files Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 15/20] attestation: Prepare provider and instance core Jiri Pirko
2026-10-15 15:30 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 16/20] attestation: Prepare measurement register journal Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 17/20] attestation: Add CTLV operation handling Jiri Pirko
2026-10-15 15:33 ` sashiko-bot
2026-10-15 14:50 ` [PATCH RFC 18/20] tdx-guest: Expose the native attestation service API Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 19/20] attestation: Add the TDX family specification and generated files Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 20/20] attestation: Add the TDX family implementation Jiri Pirko
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=sashiko-outbox-173043@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jiri@resnulli.us \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox