Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Haibo Xu <haibo1.xu@intel.com>, Anup Patel <anup@brainfault.org>
Subject: Re: [PATCH] KVM: selftests: Assert that vasprintf() is successful
Date: Thu, 14 Sep 2023 10:02:28 +0200	[thread overview]
Message-ID: <20230914-d8d1bb0c3d71454c0a55f721@orel> (raw)
In-Reply-To: <20230914010636.1391735-1-seanjc@google.com>

On Wed, Sep 13, 2023 at 06:06:36PM -0700, Sean Christopherson wrote:
> Assert that vasprintf() succeeds as the "returned" string is undefined
> on failure.  Checking the result also eliminates the only warning with
> default options in KVM selftests, i.e. is the only thing getting in the
> way of compile with -Werror.
> 
>   lib/test_util.c: In function ‘strdup_printf’:
>   lib/test_util.c:390:9: error: ignoring return value of ‘vasprintf’
>   declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
>   390 |         vasprintf(&str, fmt, ap);
>       |         ^~~~~~~~~~~~~~~~~~~~~~~~
> 

Oh, darn. My compilers didn't report that or I would have fixed it.

> Don't bother capturing the return value, allegedly vasprintf() can only
> fail due to a memory allocation failure.
> 
> Fixes: dfaf20af7649 ("KVM: arm64: selftests: Replace str_with_index with strdup_printf")
> Cc: Andrew Jones <ajones@ventanamicro.com>
> Cc: Haibo Xu <haibo1.xu@intel.com>
> Cc: Anup Patel <anup@brainfault.org>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> 
> I haven't actually run the relevant tests, someone should probably do so on
> ARM and/or RISC-V to make sure I didn't do something stupid.

Done for both.

Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Tested-by: Andrew Jones <ajones@ventanamicro.com>

Thanks,
drew

> 
>  tools/testing/selftests/kvm/lib/test_util.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/kvm/lib/test_util.c b/tools/testing/selftests/kvm/lib/test_util.c
> index 3e36019eeb4a..5d7f28b02d73 100644
> --- a/tools/testing/selftests/kvm/lib/test_util.c
> +++ b/tools/testing/selftests/kvm/lib/test_util.c
> @@ -387,7 +387,7 @@ char *strdup_printf(const char *fmt, ...)
>  	char *str;
>  
>  	va_start(ap, fmt);
> -	vasprintf(&str, fmt, ap);
> +	TEST_ASSERT(vasprintf(&str, fmt, ap) >= 0, "vasprintf() failed");
>  	va_end(ap);
>  
>  	return str;
> 
> base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
> -- 
> 2.42.0.283.g2d96d420d3-goog
> 

  reply	other threads:[~2023-09-14  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  1:06 [PATCH] KVM: selftests: Assert that vasprintf() is successful Sean Christopherson
2023-09-14  8:02 ` Andrew Jones [this message]
2023-09-20 16:29 ` Paolo Bonzini

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=20230914-d8d1bb0c3d71454c0a55f721@orel \
    --to=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=haibo1.xu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox