From: Jan Stancek <jstancek@redhat.com>
To: Li Wang <liwang@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] syscalls/sysfs: replace the TWARN to TCONF
Date: Sun, 26 Jul 2015 07:45:43 -0400 (EDT) [thread overview]
Message-ID: <1216267366.178924.1437911143948.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1437722520-2794-1-git-send-email-liwang@redhat.com>
----- Original Message -----
> From: "Li Wang" <liwang@redhat.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Friday, 24 July, 2015 9:22:00 AM
> Subject: [LTP] [PATCH] syscalls/sysfs: replace the TWARN to TCONF
>
> I run some of these cases on aarch64 today and get a series waring, that's
> because
> sysfs syscall is not implemented on aarch64. So, maybe TCONF is better than
> TWARN
> in the testcase.
Are you sure it's not supported? Or is it just disabled in your kernel config?
I'm looking at Kconfig and nothing suggests you can't use it on aarch64:
config SYSFS_SYSCALL
bool "Sysfs syscall support" if EXPERT
default y
---help---
sys_sysfs is an obsolete system call no longer supported in libc.
Note that disabling this option is more secure but might break
compatibility with some systems.
If unsure say Y here.
We have "linux_syscall_numbers.h", if you include that and use
ltp_syscall() instead of syscall() you can remove the #ifdef,
as it should TCONF at runtime (in case kernel gives you ENOSYS)
Regards,
Jan
>
> Signed-off-by: Li Wang <liwang@redhat.com>
> ---
> testcases/kernel/syscalls/sysfs/sysfs01.c | 2 +-
> testcases/kernel/syscalls/sysfs/sysfs02.c | 2 +-
> testcases/kernel/syscalls/sysfs/sysfs03.c | 2 +-
> testcases/kernel/syscalls/sysfs/sysfs04.c | 2 +-
> testcases/kernel/syscalls/sysfs/sysfs05.c | 2 +-
> testcases/kernel/syscalls/sysfs/sysfs06.c | 2 +-
> 6 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs01.c
> b/testcases/kernel/syscalls/sysfs/sysfs01.c
> index 11ebe43..c29f6c0 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs01.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs01.c
> @@ -103,7 +103,7 @@ int main(int ac, char **av)
> }
> } /*End of TEST_LOOPING */
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs02.c
> b/testcases/kernel/syscalls/sysfs/sysfs02.c
> index f7cb96a..54557cc 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs02.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs02.c
> @@ -103,7 +103,7 @@ int main(int ac, char **av)
> }
> } /*End of TEST_LOOPING */
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs03.c
> b/testcases/kernel/syscalls/sysfs/sysfs03.c
> index 59b997e..9048dfe 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs03.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs03.c
> @@ -101,7 +101,7 @@ int main(int ac, char **av)
> }
> } /*End of TEST_LOOPING */
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs04.c
> b/testcases/kernel/syscalls/sysfs/sysfs04.c
> index f4fda36..2b2530a 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs04.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs04.c
> @@ -105,7 +105,7 @@ int main(int ac, char **av)
> }
> }
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs05.c
> b/testcases/kernel/syscalls/sysfs/sysfs05.c
> index e97f0c8..2ab6707 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs05.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs05.c
> @@ -129,7 +129,7 @@ int main(int ac, char **av)
> } /*End of TEST LOOPS */
> }
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> diff --git a/testcases/kernel/syscalls/sysfs/sysfs06.c
> b/testcases/kernel/syscalls/sysfs/sysfs06.c
> index 121e944..7ef5ee2 100644
> --- a/testcases/kernel/syscalls/sysfs/sysfs06.c
> +++ b/testcases/kernel/syscalls/sysfs/sysfs06.c
> @@ -132,7 +132,7 @@ int main(int ac, char **av)
> } /*End of TEST LOOPS */
> }
> #else
> - tst_resm(TWARN,
> + tst_resm(TCONF,
> "This test can only run on kernels that support the sysfs system call");
> #endif
>
> --
> 1.8.3.1
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-07-26 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 7:22 [LTP] [PATCH] syscalls/sysfs: replace the TWARN to TCONF Li Wang
2015-07-26 11:45 ` Jan Stancek [this message]
2015-07-27 5:54 ` Li Wang
2015-07-27 7:34 ` Jan Stancek
2015-07-27 8:27 ` Li Wang
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=1216267366.178924.1437911143948.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=liwang@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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.