From: Shuah Khan <skhan@linuxfoundation.org>
To: Yiwei Lin <s921975628@gmail.com>, trenn@suse.com, shuah@kernel.org
Cc: jwyatt@redhat.com, jkacur@redhat.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] cpupower: monitor: Exit with error status if execvp() fail
Date: Thu, 20 Feb 2025 09:33:22 -0700 [thread overview]
Message-ID: <24f77be1-5b91-4b4b-93eb-4be5d8bd32c1@linuxfoundation.org> (raw)
In-Reply-To: <20250220130529.4515-1-s921975628@gmail.com>
On 2/20/25 06:05, Yiwei Lin wrote:
> In the case that we give a invalid command to idle_monitor for
> monitoring, the execvp() will fail and thus go to the next line.
> As a result, we'll see two differnt monitoring output. For
> example, running `cpupower monitor -i 5 invalidcmd` which `invalidcmd`
> is not executable.
>
> ---
> V2:
> - fix according to review from Shuah
> ---
>
> Signed-off-by: Yiwei Lin <s921975628@gmail.com>
> ---
> tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c b/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> index f746099b5dac..7f8958f68eaa 100644
> --- a/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> +++ b/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> @@ -6,6 +6,7 @@
> */
>
>
> +#include <errno.h>
> #include <stdio.h>
> #include <unistd.h>
> #include <stdlib.h>
> @@ -294,7 +295,10 @@ int fork_it(char **argv)
>
> if (!child_pid) {
> /* child */
> - execvp(argv[0], argv);
> + if (execvp(argv[0], argv) == -1) {
> + printf("Fail to execute %s\n", argv[0]);
Invalid monitor command will be a better message than
saying "failed to execute"
thanks,
-- Shuahg
prev parent reply other threads:[~2025-02-20 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:05 Yiwei Lin
2025-02-20 16:33 ` Shuah Khan [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=24f77be1-5b91-4b4b-93eb-4be5d8bd32c1@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=s921975628@gmail.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.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
all inboxes | Powered by JetHome®