From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Jan Beulich" <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, "Juergen Gross" <jgross@suse.com>
Subject: Re: [PATCH] libxc/PM: correct (not just) error handling in xc_get_cpufreq_para()
Date: Fri, 28 Mar 2025 10:51:27 +0000 [thread overview]
Message-ID: <Z-Z_LokdcNj_K_g5@l14> (raw)
In-Reply-To: <df676738-19e7-47e6-977f-25d6d13ccc50@suse.com>
On Thu, Mar 27, 2025 at 02:32:04PM +0100, Jan Beulich wrote:
> HWP work made the cleanup of the "available governors" array
> conditional, neglecting the fact that the condition used may not be the
I don't know why the cleanup was made conditional, as long as the bounce
buffer is declared with DECLARE_NAMED_HYPERCALL_BOUNCE(),
xc_hypercall_bounce_post() can be called without issue (even if
..bounce_pre isn't used). Maybe it's all those "unlock_*" labels that is
misleading, a single "out" label which does the cleanup
unconditionally would be more than enough.
> condition that was used to allocate the buffer (as the structure field
> is updated upon getting back EAGAIN). Throughout the function, use the
> local variable being introduced to address that.
>
> --- a/tools/libs/ctrl/xc_pm.c
> +++ b/tools/libs/ctrl/xc_pm.c
> @@ -212,31 +212,32 @@ int xc_get_cpufreq_para(xc_interface *xc
> DECLARE_NAMED_HYPERCALL_BOUNCE(scaling_available_governors,
> user_para->scaling_available_governors,
> user_para->gov_num * CPUFREQ_NAME_LEN * sizeof(char), XC_HYPERCALL_BUFFER_BOUNCE_BOTH);
> -
> - bool has_num = user_para->cpu_num &&
> - user_para->freq_num &&
> - user_para->gov_num;
> + unsigned int in_gov_num = user_para->gov_num;
> + bool has_num = user_para->cpu_num && user_para->freq_num;
>
> if ( has_num )
I think there's an issue here, this condition used to be true if
`gov_num` was not 0, even if `cpu_num` and `freq_num` was 0. That's not
the case anymore. Shouldn't `has_num` use also the value from
`gov_num`? Do we actually need `has_num`?
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2025-03-28 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 13:32 [PATCH] libxc/PM: correct (not just) error handling in xc_get_cpufreq_para() Jan Beulich
2025-03-28 10:51 ` Anthony PERARD [this message]
2025-03-28 11:06 ` Jan Beulich
2025-04-07 11:38 ` Ping: " Jan Beulich
2025-04-07 12:45 ` Anthony PERARD
2025-04-07 13:23 ` Jan Beulich
2025-04-07 15:23 ` Anthony PERARD
2025-04-07 15:38 ` Jan Beulich
2025-04-08 9:59 ` Anthony PERARD
2025-04-08 10:47 ` Jan Beulich
2025-04-08 11:47 ` Anthony PERARD
2025-04-07 20:36 ` Jason Andryuk
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=Z-Z_LokdcNj_K_g5@l14 \
--to=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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.