All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "seanjc@google.com" <seanjc@google.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"thorsten.blum@linux.dev" <thorsten.blum@linux.dev>,
	"bp@alien8.de" <bp@alien8.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"kas@kernel.org" <kas@kernel.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] KVM: TDX: Use struct_size and simplify tdx_get_capabilities
Date: Wed, 12 Nov 2025 19:59:13 +0000	[thread overview]
Message-ID: <4a2a74e01bfd31bc4bd7a672452c2d3d513c33db.camel@intel.com> (raw)
In-Reply-To: <20251112171630.3375-1-thorsten.blum@linux.dev>

On Wed, 2025-11-12 at 18:16 +0100, Thorsten Blum wrote:

kvm x86 logs are suggested to start with a short summary of the patch. Maybe:

Simplify the logic for copying the KVM_TDX_CAPABILITIES struct to userspace.


It looks like you are conducting a treewide pattern matching cleanup?

> > Retrieve the number of user entries with get_user() first and return
> > -E2BIG early if 'user_caps' is too small to fit 'caps'.
> > 
> > Allocate memory for 'caps' only after checking the user buffer's number
> > of entries, thus removing two gotos and the need for premature freeing.
> > 
> > Use struct_size() instead of manually calculating the number of bytes to
> > allocate for 'caps', including the nested flexible array.
> > 
> > Finally, copy 'caps' to user space with a single copy_to_user() call.

In the handling of get_user(nr_user_entries, &user_caps->cpuid.nent), the old
code forced -EFAULT, this patch doesn't. But it leaves the copy_to_user()'s to
still force EFAULT. Why?


Tested-by: Rick Edgecombe <rick.p.edgecombe@intel.com> (really the TDX CI)

> > 
> > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> > ---
> >  arch/x86/kvm/vmx/tdx.c | 32 ++++++++++++--------------------
> >  1 file changed, 12 insertions(+), 20 deletions(-)
> > 
> > diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
> > index 0a49c863c811..23d638b4a003 100644
> > --- a/arch/x86/kvm/vmx/tdx.c
> > +++ b/arch/x86/kvm/vmx/tdx.c
> > @@ -2282,37 +2282,29 @@ static int tdx_get_capabilities(struct kvm_tdx_cmd *cmd)
> >  	if (cmd->flags)
> >  		return -EINVAL;
> >  
> > -	caps = kzalloc(sizeof(*caps) +
> > -		       sizeof(struct kvm_cpuid_entry2) * td_conf->num_cpuid_config,
> > -		       GFP_KERNEL);
> > -	if (!caps)
> > -		return -ENOMEM;
> > -
> >  	user_caps = u64_to_user_ptr(cmd->data);
> > -	if (get_user(nr_user_entries, &user_caps->cpuid.nent)) {
> > -		ret = -EFAULT;
> > -		goto out;
> > -	}
> > +	ret = get_user(nr_user_entries, &user_caps->cpuid.nent);
> > +	if (ret)
> > +		return ret;
> >  
> > -	if (nr_user_entries < td_conf->num_cpuid_config) {
> > -		ret = -E2BIG;
> > -		goto out;
> > -	}
> > +	if (nr_user_entries < td_conf->num_cpuid_config)
> > +		return -E2BIG;
> > +
> > +	caps = kzalloc(struct_size(caps, cpuid.entries,
> > +				   td_conf->num_cpuid_config), GFP_KERNEL);
> > +	if (!caps)
> > +		return -ENOMEM;
> >  
> >  	ret = init_kvm_tdx_caps(td_conf, caps);
> >  	if (ret)
> >  		goto out;
> >  
> > -	if (copy_to_user(user_caps, caps, sizeof(*caps))) {
> > +	if (copy_to_user(user_caps, caps, struct_size(caps, cpuid.entries,
> > +						      caps->cpuid.nent))) {
> >  		ret = -EFAULT;
> >  		goto out;
> >  	}
> >  
> > -	if (copy_to_user(user_caps->cpuid.entries, caps->cpuid.entries,
> > -			 caps->cpuid.nent *
> > -			 sizeof(caps->cpuid.entries[0])))
> > -		ret = -EFAULT;
> > -
> >  out:
> >  	/* kfree() accepts NULL. */
> >  	kfree(caps);


  reply	other threads:[~2025-11-12 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 17:16 [PATCH RESEND] KVM: TDX: Use struct_size and simplify tdx_get_capabilities Thorsten Blum
2025-11-12 19:59 ` Edgecombe, Rick P [this message]
2025-11-12 20:24   ` Sean Christopherson
2025-11-13  0:41     ` Edgecombe, Rick P
2025-11-13 16:29       ` Sean Christopherson
2025-11-13 18:49         ` Edgecombe, Rick P
2025-11-13 18:55           ` Sean Christopherson
2025-11-12 21:22   ` Thorsten Blum

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=4a2a74e01bfd31bc4bd7a672452c2d3d513c33db.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=thorsten.blum@linux.dev \
    --cc=x86@kernel.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.