From: Anibal Limon <anibal@limonsoftware.com>
To: yocto@lists.yoctoproject.org
Cc: richard.purdie@linuxfoundation.org, JPEWhacker@gmail.com,
randy.macleod@windriver.com,
Anibal Limon <anibal@limonsoftware.com>
Subject: [yocto][ptest-runner 2/2] utils: run_child fix security flags build
Date: Sat, 27 Jan 2024 13:23:38 -0600 [thread overview]
Message-ID: <20240127192338.776610-2-anibal@limonsoftware.com> (raw)
In-Reply-To: <20240127192338.776610-1-anibal@limonsoftware.com>
Move chdir outside run_child to better handle when fails output an error
message plus remove the need to strdup inside run_child (already have
ptest_dir).
Signed-off-by: Anibal Limon <anibal@limonsoftware.com>
---
utils.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/utils.c b/utils.c
index 54394cc..472520f 100644
--- a/utils.c
+++ b/utils.c
@@ -327,7 +327,6 @@ static inline void
run_child(char *run_ptest, int fd_stdout, int fd_stderr)
{
char *const argv[2] = {run_ptest, NULL};
- chdir(dirname(strdup(run_ptest)));
dup2(fd_stdout, STDOUT_FILENO);
// XXX: Redirect stderr to stdout to avoid buffer ordering problems.
@@ -466,7 +465,11 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
fprintf(fp, "ERROR: Unable to attach to controlling tty, %s\n", strerror(errno));
}
- run_child(p->run_ptest, pipefd_stdout[PIPE_WRITE], pipefd_stderr[PIPE_WRITE]);
+ if (chdir(ptest_dir) == -1) {
+ fprintf(fp, "ERROR: Unable to chdir(%s), %s\n", ptest_dir, strerror(errno));
+ } else {
+ run_child(p->run_ptest, pipefd_stdout[PIPE_WRITE], pipefd_stderr[PIPE_WRITE]);
+ }
} else {
bool timedout = false;
--
2.43.0
prev parent reply other threads:[~2024-01-27 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 19:23 [yocto][ptest-runner 1/2] utils.c: get_available_ptests fix security flags compilation Anibal Limon
2024-01-27 19:23 ` Anibal Limon [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=20240127192338.776610-2-anibal@limonsoftware.com \
--to=anibal@limonsoftware.com \
--cc=JPEWhacker@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox