From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v7 4/4] syscalls/fsmount01: Add test for fsmount series API
Date: Mon, 17 Feb 2020 10:38:50 +0100 [thread overview]
Message-ID: <20200217093850.GA13398@dell5510> (raw)
In-Reply-To: <CAEemH2cGsXkgkfrFN2XW9ByWqNnknR+-9yCv6T+hqAp13PjVyQ@mail.gmail.com>
Hi Li,
> > NOTE: most of the syscalls numbers were added in previous commits
> > (c2f27f6e9b, 01e4dc2222, 87a2612857).
> 87a2612857 is invalid?
I'm sorry, that was this upcomming commit (besides that it needs to be removed
from it) => thanks for a report, I'll remove it.
> > Signed-off-by: Zorro Lang <zlang@redhat.com>
> > Acked-by: Li Wang <liwang@redhat.com>
> > [ pvorel: rebased, cleanup autotools and other small fixes ]
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > include/lapi/syscalls/powerpc64.in | 4 +
> > runtest/syscalls | 2 +
> > testcases/kernel/syscalls/fsmount/.gitignore | 1 +
> > testcases/kernel/syscalls/fsmount/Makefile | 8 ++
> > testcases/kernel/syscalls/fsmount/fsmount01.c | 95 +++++++++++++++++++
> > 5 files changed, 110 insertions(+)
> > create mode 100644 testcases/kernel/syscalls/fsmount/.gitignore
> > create mode 100644 testcases/kernel/syscalls/fsmount/Makefile
> > create mode 100644 testcases/kernel/syscalls/fsmount/fsmount01.c
> > diff --git a/include/lapi/syscalls/powerpc64.in b/include/lapi/syscalls/
> > powerpc64.in
> > index 2c1f105c1..beb0e6812 100644
> > --- a/include/lapi/syscalls/powerpc64.in
> > +++ b/include/lapi/syscalls/powerpc64.in
> > @@ -371,3 +371,7 @@ pidfd_open 434
> > pkey_mprotect 386
> > pkey_alloc 384
> > pkey_free 385
> > +move_mount 429
> > +fsopen 430
> > +fsconfig 431
> > +fsmount 432
Yep.
> As Viresh and I commented in the previous email this four syscalls-number
> should be deleted from the patch.
> Besides that, the patchset looks good to me.
> Acked-by: Li Wang <liwang@redhat.com>
I suppose you ack also the change include/lapi/fsmount.h using lapi/fcntl.h
(if not, please let me know).
Kind regards,
Petr
next prev parent reply other threads:[~2020-02-17 9:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 8:46 [LTP] [PATCH v7 0/4] Add test for new mount API v5.2 Petr Vorel
2020-02-17 8:46 ` [LTP] [PATCH v7 1/4] tst_umount: Fail immediately when errno != EBUSY Petr Vorel
2020-02-17 8:46 ` [LTP] [PATCH v7 2/4] safe_macros: Use tst_umount() in safe_umount() Petr Vorel
2020-02-17 8:46 ` [LTP] [PATCH v7 3/4] lapi/fsmount: Add definitions for fsmount related syscalls Petr Vorel
2020-02-17 13:49 ` Cyril Hrubis
2020-02-17 8:46 ` [LTP] [PATCH v7 4/4] syscalls/fsmount01: Add test for fsmount series API Petr Vorel
2020-02-17 9:16 ` Li Wang
2020-02-17 9:38 ` Petr Vorel [this message]
2020-02-17 13:52 ` Cyril Hrubis
2020-02-17 14:04 ` Petr Vorel
2020-02-17 14:13 ` Petr Vorel
2020-02-17 15:02 ` Petr Vorel
2020-02-17 9:14 ` [LTP] [PATCH v7 0/4] Add test for new mount API v5.2 Viresh Kumar
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=20200217093850.GA13398@dell5510 \
--to=pvorel@suse.cz \
--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