From: Petr Vorel <pvorel@suse.cz>
To: Edward Liaw <edliaw@google.com>
Cc: kernel-team@android.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] getpgid01: On Android, pgid(1) is 0 instead of 1
Date: Mon, 30 Oct 2023 08:40:45 +0100 [thread overview]
Message-ID: <20231030074045.GB9167@pevik> (raw)
In-Reply-To: <20231027190029.3820505-1-edliaw@google.com>
Hi Edward,
> Android's init does not call setpgid(0, 0) so it does not have pgid=1.
> In either case, the pgid should match /proc/1/stat, so compare
> getpgid(1) against that.
> Signed-off-by: Edward Liaw <edliaw@google.com>
> ---
> testcases/kernel/syscalls/getpgid/getpgid01.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
> diff --git a/testcases/kernel/syscalls/getpgid/getpgid01.c b/testcases/kernel/syscalls/getpgid/getpgid01.c
> index 479fe5dcb..de05a434b 100644
> --- a/testcases/kernel/syscalls/getpgid/getpgid01.c
> +++ b/testcases/kernel/syscalls/getpgid/getpgid01.c
> @@ -13,6 +13,14 @@
> #include "tst_test.h"
> +static int get_init_pgid()
static int get_init_pgid(void)
We still use -std=gnu99, thus we need that otherwise compiler complains
warning: old-style function definition [-Wold-style-definition].
It can be fixed during merge.
Kind regards,
Petr
> +{
> + int pgid;
> +
> + SAFE_FILE_SCANF("/proc/1/stat", "%*d %*s %*c %*d %d", &pgid);
> + return pgid;
> +}
> +
> static void run(void)
> {
> pid_t pid_1, child_pid, pgid;
> @@ -37,7 +45,7 @@ static void run(void)
> TST_EXP_EQ_LI(TST_RET, pgid);
> TST_EXP_PID(getpgid(1));
> - TST_EXP_EQ_LI(TST_RET, 1);
> + TST_EXP_EQ_LI(TST_RET, get_init_pgid());
> }
> tst_reap_children();
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-30 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 19:00 [LTP] [PATCH v3] getpgid01: On Android, pgid(1) is 0 instead of 1 Edward Liaw via ltp
2023-10-30 7:40 ` Petr Vorel [this message]
2023-10-30 10:06 ` Cyril Hrubis
2023-10-30 11:06 ` Petr Vorel
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=20231030074045.GB9167@pevik \
--to=pvorel@suse.cz \
--cc=edliaw@google.com \
--cc=kernel-team@android.com \
--cc=ltp@lists.linux.it \
/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