* [PATCH v2] cpupower: monitor: Exit with error status if execvp() fail
@ 2025-02-20 13:05 Yiwei Lin
2025-02-20 16:33 ` Shuah Khan
0 siblings, 1 reply; 2+ messages in thread
From: Yiwei Lin @ 2025-02-20 13:05 UTC (permalink / raw)
To: trenn, shuah; +Cc: jwyatt, jkacur, linux-pm, linux-kernel, Yiwei Lin
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]);
+ exit(errno);
+ }
} else {
/* parent */
if (child_pid == -1) {
--
2.34.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v2] cpupower: monitor: Exit with error status if execvp() fail
2025-02-20 13:05 [PATCH v2] cpupower: monitor: Exit with error status if execvp() fail Yiwei Lin
@ 2025-02-20 16:33 ` Shuah Khan
0 siblings, 0 replies; 2+ messages in thread
From: Shuah Khan @ 2025-02-20 16:33 UTC (permalink / raw)
To: Yiwei Lin, trenn, shuah
Cc: jwyatt, jkacur, linux-pm, linux-kernel, Shuah Khan
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-02-20 16:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-20 13:05 [PATCH v2] cpupower: monitor: Exit with error status if execvp() fail Yiwei Lin
2025-02-20 16:33 ` Shuah Khan
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®