From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscall02: add invalid syscall number test
Date: Tue, 30 Jun 2026 12:20:26 +0200 [thread overview]
Message-ID: <20260630102026.GB417625@pevik> (raw)
In-Reply-To: <akMN_kOtke47w0-v@autotest-wegao.qe.prg2.suse.org>
Hi Andrea, Wei,
> > Add a test verifying that syscall() returns ENOSYS when called with
> > unimplemented syscall numbers. The chosen numbers stay above the syscall
> > table and below the architecture-specific private ranges, so they are
> > reliably invalid on every supported architecture.
+1
Reviewed-by: Petr Vorel <pvorel@suse.cz>
...
> > +++ b/testcases/kernel/syscalls/syscall/syscall02.c
> > @@ -0,0 +1,47 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * Copyright (c) 2026 Andrea Cervesato <andrea.cervesato@suse.com>
> > + */
> > +
> > +/*\
> > + * Verify that :manpage:`syscall(2)` fails with ENOSYS when invoked with
> > + * invalid syscall numbers.
> > + *
> > + * The syscall number is dispatched as an unsigned value on Linux. A value is
> > + * reliably unimplemented on every supported architecture when it is:
> > + *
> > + * - above the syscall table
> > + * - below the architecture-specific private syscall ranges (e.g. ARM's
> > + * 0x0f0000 base)
> > + * - without the x32 ABI bit (0x40000000) set
> > + *
> > + * Such a number is routed to sys_ni_syscall and returns ENOSYS.
> > + */
> > +
> > +#include <unistd.h>
> > +#include <sys/syscall.h>
> > +
> > +#include "tst_test.h"
> > +
> > +#define TC(x) {.scno = (long)(x), .desc = #x}
> > +
> > +static struct tcase {
> > + long scno;
> > + const char *desc;
> > +} tcases[] = {
> > + TC(0x8000),
> > + TC(0xf000),
> > + TC(0xfffe),
> > +};
> I suggest add two more cases check:
> 1) -1
> 2) __NR_syscalls +1 (Base arch/powerpc/kernel/syscall.c)
+1. Something like this wouldn't harm (tested only on x86_64 and x86).
Kind regards,
Petr
+++ testcases/kernel/syscalls/syscall/syscall02.c
@@ -14,12 +14,15 @@
* - below the architecture-specific private syscall ranges (e.g. ARM's
* 0x0f0000 base)
* - without the x32 ABI bit (0x40000000) set
+ * - -1
+ * - __NR_syscalls + 1
*
* Such a number is routed to sys_ni_syscall and returns ENOSYS.
*/
#include <unistd.h>
#include <sys/syscall.h>
+#include <asm-generic/unistd.h>
#include "tst_test.h"
@@ -32,6 +35,8 @@ static struct tcase {
TC(0x8000),
TC(0xf000),
TC(0xfffe),
+ TC(-1),
+ TC(__NR_syscalls + 1),
};
static void verify_syscall(unsigned int n)
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-30 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:03 [LTP] [PATCH] syscall02: add invalid syscall number test Andrea Cervesato
2026-06-29 14:53 ` [LTP] " linuxtestproject.agent
2026-06-30 0:29 ` [LTP] [PATCH] " Wei Gao via ltp
2026-06-30 10:20 ` Petr Vorel [this message]
2026-06-30 10:57 ` Andrea Cervesato via ltp
2026-06-30 16:40 ` Petr Vorel
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=20260630102026.GB417625@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=wegao@suse.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