From: Cyril Hrubis <chrubis@suse.cz>
To: zhaogongyi <zhaogongyi@huawei.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls/fork02: new test for fork()
Date: Wed, 2 Nov 2022 10:06:32 +0100 [thread overview]
Message-ID: <Y2IzGBIyAoA7fm2m@yuki> (raw)
In-Reply-To: <0aaeb7d55c194ca79b2958dc8c4e5204@huawei.com>
Hi!
> > > Man-pages does not menthion this, and the other field inherited does
> > not mentioned too.
> >
> > I guess that this is described in POSIX in:
> >
> > "The new process (child process) shall be an exact copy of the calling
> > process (parent process) except as detailed below:"
> >
> > at https://pubs.opengroup.org/onlinepubs/9699919799/
> >
> > And there is nothing about working dir in the list of special cases hence
> > working dir is exactly the same as for parent since it has to be exact copy
> > of parent.
> >
>
> It seems reasonable to not test the result of full inheritance from the parent process, otherwise there are a lot of testcases.
Certainly the interesting part would be testing all the exceptions, but
having one test that checks a few things that are supposed to be the
same wouldn't harm either.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-02 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 1:05 [LTP] [PATCH] syscalls/fork02: new test for fork() zhaogongyi via ltp
2022-11-02 9:06 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 2:51 zhaogongyi via ltp
2022-10-25 2:30 zhaogongyi via ltp
2022-10-31 13:46 ` Cyril Hrubis
2022-10-21 6:50 Zhao Gongyi via ltp
2022-10-25 2:18 ` xuyang2018.jy
2022-11-07 10:49 ` Richard Palethorpe
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=Y2IzGBIyAoA7fm2m@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=zhaogongyi@huawei.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