From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/3] syscalls/pipe2_03: Add new test for pipe2 O_DIRECT flag
Date: Wed, 22 Apr 2020 18:05:06 +0800 [thread overview]
Message-ID: <CAEemH2d6ObRfR12xvfpmE9KtTakobzvt6_md=Xrmd_rbKB7oAA@mail.gmail.com> (raw)
In-Reply-To: <20f5e406-f430-79ba-f911-015247e73d0d@cn.fujitsu.com>
On Wed, Apr 22, 2020 at 5:31 PM Yang Xu <xuyang2018.jy@cn.fujitsu.com>
wrote:
> ...
> >>> I think I got the point.
> >>>
> >>> In your test code for pipe2(), you didn't use pipe in the correct
> >>> way. Even that we define the fds[2] as a global variable, there still
> >>> have a new copy for fds[2] in the child process, we should close one
> >>> of the pipes in child and parent to make the connection is built
> >>> correspondingly, then that will work normally for us.
> >>>
> >>> I suggest redesigning some of the test structs. What do you think?
> >> Yes.
> >>>
> >>> Fyi:
> >>>
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/pipe/pipe02.c
> >
> > BTW, pipe02.c can use SAFE_PIPE macro and remove UCLINUX ifdef.
> >>>
> >> In principle, we should use the following format
> >> step1 pipe(fds);
> >> step2 SAFE_FORK();
> >> child process
> >> step3 close one fd and do something
> >> parent process
> >> step4 close another fd and do something
> >>
> >> Also, we should not do write opeartion in step 1~2, otherwise child
> >> process will inherit data.
> modify this case ,url as below:
>
> https://github.com/xuyang0410/ltp/commit/6e701803b39123b5abf74bd292c36fee73b54065
>
> How about it?
>
I leave comment in your patch in github. Thanks for the quick fix, the rest
LGTM.
Can you rebase the code on the latest master and format V4 patch to ML?
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200422/7623f96e/attachment.htm>
next prev parent reply other threads:[~2020-04-22 10:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:52 [LTP] [PATCH] syscalls/pipe2_01: convert into new API Yang Xu
2020-04-15 5:11 ` [LTP] [PATCH v2] " Yang Xu
2020-04-16 7:28 ` [LTP] [PATCH v3 0/3] increase pipe2 coverage Yang Xu
2020-04-16 7:29 ` [LTP] [PATCH v3 1/3] syscalls/pipe2_01: convert into new API Yang Xu
2020-04-21 8:19 ` Li Wang
2020-04-21 8:27 ` Yang Xu
2020-04-16 7:29 ` [LTP] [PATCH v3 2/3] syscalls/pipe2_02: Add new test for pipe2 O_CLOEXEC flag Yang Xu
2020-04-21 8:49 ` Li Wang
2020-04-21 9:41 ` Yang Xu
2020-04-21 9:59 ` Li Wang
2020-04-16 7:29 ` [LTP] [PATCH v3 3/3] syscalls/pipe2_03: Add new test for pipe2 O_DIRECT flag Yang Xu
2020-04-17 9:44 ` Li Wang
2020-04-17 9:56 ` Yang Xu
2020-04-17 10:13 ` Li Wang
2020-04-17 10:50 ` Li Wang
2020-04-21 9:53 ` Li Wang
2020-04-21 10:21 ` Yang Xu
2020-04-22 6:05 ` Li Wang
2020-04-22 6:14 ` Yang Xu
2020-04-22 7:29 ` Li Wang
2020-04-22 8:08 ` Yang Xu
2020-04-22 8:12 ` Yang Xu
2020-04-22 9:31 ` Yang Xu
2020-04-22 10:05 ` Li Wang [this message]
2020-04-22 10:06 ` Yang Xu
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='CAEemH2d6ObRfR12xvfpmE9KtTakobzvt6_md=Xrmd_rbKB7oAA@mail.gmail.com' \
--to=liwang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.