Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jiri Pirko" <jiri@resnulli.us>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH RFC 20/20] attestation: Add the TDX family implementation
Date: Thu, 15 Oct 2026 15:40:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-173084@kernel.org> (raw)
In-Reply-To: <20261015145053.3664509-21-jiri@resnulli.us>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] mm: memory accounting bypass via missing __GFP_ACCOUNT in attestation_tdx_evidence_get
--

commit 70d54896a73342be7665edff009c1c4b80f13008
Author: Jiri Pirko <jiri@nvidia.com>

attestation: Add the TDX family implementation

This commit connects the attestation family to the native TDX service. It
exposes TDREPORT, Quote, MRTD, and RTMR operations while preserving the
existing native interfaces.

> diff --git a/drivers/attestation/providers/tdx.c b/drivers/attestation/providers/tdx.c
> new file mode 100644
> --- /dev/null
> +++ b/drivers/attestation/providers/tdx.c

[ ... ]

> +static int
> +attestation_tdx_evidence_get(struct attestation *att,
> +			     const struct attestation_evidence_request *request,
> +			     struct attestation_evidence_result *result)
> +{
> +	const struct attestation_evidence_object_request *object;
> +	struct attestation_tdx *tdx = ctlv_priv_child(att);
> +	size_t length;
> +	void *buffer;
> +	int ret;
> +
> +	if (request->objects_count != 1)
> +		return -EOPNOTSUPP;
> +	object = &request->objects[0];
> +	buffer = kvmalloc(object->supported_object->max_length, GFP_KERNEL);

[Severity: Medium]
Does this allocation need the __GFP_ACCOUNT flag?

The buffer size for a TDX Quote can be up to TDX_GUEST_QUOTE_MAX_LEN
(approximately 128KB). This operation proceeds to call
tdx->ops->quote_get(), which acquires the global quote_lock mutex in the
tdx-guest driver.

If userspace issues concurrent quote requests, tasks will block on this
mutex while holding these large, unaccounted buffers. Can this allow a
container to accumulate a significant amount of kernel memory that bypasses
memcg limits, potentially leading to host out-of-memory conditions?

> +	if (!buffer)
> +		return -ENOMEM;
> +	if (object->supported_object == &attestation_tdx_evidence_objects[0])
> +		ret = tdx->ops->report_get(tdx->parent_dev,

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261015145053.3664509-1-jiri@resnulli.us?part=20

      reply	other threads:[~2026-10-15 15:40 UTC|newest]

Thread overview: 32+ 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
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 15:40   ` sashiko-bot
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
2026-10-15 15:40   ` sashiko-bot [this message]

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-173084@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