From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/cma: test case should return TCONF if syscall doesn't exist
Date: Tue, 4 Dec 2018 03:54:01 -0500 (EST) [thread overview]
Message-ID: <1514394255.82007574.1543913641122.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5C05EB31.1030707@linux.alibaba.com>
----- Original Message -----
>
>
> On 2018/12/3 下午5:58, Jan Stancek wrote:
> >
> >
> > ----- Original Message -----
> >> The original code returns TFAIL when process_vm_readv/_writev syscalls
> >> do not exist, while we are expecting a TCONF. During investigation, we
> >> find it is due to '#if defined(__NR_process_vm_readv/_writev)' fails to
> >> work as expected. We fix this issue by using ltp_syscall() function in
> >> setup function. BTW, we don't use new tst_syscall() interface due to
> >> compatibility issue exists between old apis and new ones.
> >
> > Fine by me, but then you should also add syscall numbers to
> > include/lapi/syscalls:
> >
>
> Thanks.
> I have TWO questions:
>
> 1. If I use this command #./strip_syscall.awk
> /usr/include/asm/unistd_64.h > x86_64.in, it will update and add more
> new syscall numbers into x86_64.in file which includes many other
> syscall numbers not only process_vm_readv/_writev. To solve this
> problem, can I just add the process_vm_readv/_writev syscall numbers and
> let go of other numbers?
Yes, I think updating only syscalls your patch is touching would be preferred.
>
> 2. I don't have so many types of machines that support different
> architectures like hppa and s390x. So what should I do to know this
> syscall number on other architectures. I'm running the tests on x86_64 arch.
You can find it in kernel sources, e.g. grep for it, or usually
one of first commits mentioning the syscall will also add number.
Regards,
Jan
>
> Jason
>
> > process_vm01.c: In function ‘setup’:
> > process_vm01.c:97: warning: unused parameter ‘argv’
> > process_vm01.c: In function ‘cma_test_params_read’:
> > process_vm01.c:127: error: ‘__NR_process_vm_readv’ undeclared (first use in
> > this function)
> > process_vm01.c:127: error: (Each undeclared identifier is reported only
> > once
> > process_vm01.c:127: error: for each function it appears in.)
> > process_vm01.c: In function ‘cma_test_params_write’:
> > process_vm01.c:136: error: ‘__NR_process_vm_writev’ undeclared (first use
> > in this function)
> >
> > Regards,
> > Jan
> >
>
next prev parent reply other threads:[~2018-12-04 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 9:43 [LTP] [PATCH] syscalls/cma: test case should return TCONF if syscall doesn't exist Jason Xing
2018-12-03 9:58 ` Jan Stancek
2018-12-04 2:49 ` Jason Xing
2018-12-04 8:54 ` Jan Stancek [this message]
2018-12-05 13:43 ` [LTP] [PATCH v2 1/2] " Jason Xing
2018-12-05 13:43 ` [LTP] [PATCH v2 2/2] lapi/syscalls: Add syscall numbers for process_vm_readv/_writev Jason Xing
2018-12-05 22:07 ` Petr Vorel
2018-12-06 3:37 ` Jason Xing
2019-02-15 10:50 ` [LTP] [PATCH v2 1/2] syscalls/cma: test case should return TCONF if syscall doesn't exist Li Wang
2019-02-15 13:53 ` Jan Stancek
2019-02-16 7:18 ` Li Wang
2019-02-16 10:28 ` Jan Stancek
2019-02-22 18:29 ` Jan Stancek
2019-02-23 6:21 ` Caspar Zhang
2019-02-25 8:22 ` [LTP] [PATCH] syscalls/cma: fix the failure of compiling with O2 option Jason Xing
2019-02-25 10:34 ` Li Wang
2019-02-25 10:47 ` Jan Stancek
2019-02-25 13:16 ` Caspar Zhang
2019-02-26 1:42 ` [LTP] [PATCH v2] " Jason Xing
2019-02-26 2:22 ` [LTP] [PATCH v3] " Jason Xing
2019-02-26 3:17 ` Li Wang
2019-02-26 16:03 ` Jan Stancek
2019-02-26 2:00 ` [LTP] [PATCH] " Jason Xing
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=1514394255.82007574.1543913641122.JavaMail.zimbra@redhat.com \
--to=jstancek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox