From: kernel test robot <oliver.sang@intel.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
Mukesh Kumar Chaurasiya <mkchauras@gmail.com>,
Jinjie Ruan <ruanjinjie@huawei.com>, <oliver.sang@intel.com>
Subject: [tip:core/entry] [x86/entry] 1b1f3b3e1b: kselftests.x86.syscall_numbering_64.fail
Date: Thu, 6 Aug 2026 16:32:17 +0800 [thread overview]
Message-ID: <202608061019.b3aca16-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3283 bytes --]
Hello,
kernel test robot noticed "kselftests.x86.syscall_numbering_64.fail" on:
commit: 1b1f3b3e1b3945ae6e49081fd3586a6833d4a555 ("x86/entry: Get rid of the sys_ni_syscall() indirection")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git core/entry
in testcase: kselftests
version: kselftests-x86_64-f5098b6bae76-1_20260727
with following parameters:
group: x86
config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202608061019.b3aca16-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260806/202608061019.b3aca16-lkp@intel.com
836 # timeout set to 300
837 # selftests: x86: syscall_numbering_64
838 # [RUN] Checking for x32 by calling x32 getpid()
839 # [INFO] x32 is not supported
840 # [RUN] Running tests without ptrace...
841 # [RUN] Checking system calls with msb = 0 (0x0)
842 # [RUN] Checking some common syscalls as 64 bit
843 # [OK] x64 syscall 0:0 returned 0 as expected
844 # [OK] x64 syscall 0:1 returned 0 as expected
845 # [RUN] Checking some 64-bit only syscalls as 64 bit
846 # [OK] x64 syscall 0:19 returned 0 as expected
847 # [OK] x64 syscall 0:20 returned 0 as expected
...
1452 # [RUN] Checking out of range system calls
1453 # [FAIL] x32 syscall 0:-64 returned -9999, but it should have returned -ENOSYS
1454 # [FAIL] x32 syscall 0:-63 returned -9999, but it should have returned -ENOSYS
1455 # [FAIL] x32 syscall 0:-62 returned -9999, but it should have returned -ENOSYS
1456 # [FAIL] x32 syscall 0:-61 returned -9999, but it should have returned -ENOSYS
1457 # [FAIL] x32 syscall 0:-60 returned -9999, but it should have returned -ENOSYS
1458 # [FAIL] x32 syscall 0:-59 returned -9999, but it should have returned -ENOSYS
1459 # [FAIL] x32 syscall 0:-58 returned -9999, but it should have returned -ENOSYS
... <huge number of these stuffs>
until ...
39542 # [FAIL] x32 syscall -2147483647:996 returned -9999, but it should have returned -ENOSYS
39543 # [FAIL] x32 syscall -2147483647:997 returned -9999, but it should have returned -ENOSYS
39544 # [FAIL] x32 syscall -2147483647:998 returned -9999, but it should have returned -ENOSYS
39545 # [FAIL] x32 syscall -2147483647:999 returned -9999, but it should have returned -ENOSYS
39546 # [FAIL] x32 syscalls -2147483647:0..999 had 1000 failure
39547 # [FAIL] A total of 37800 system calls had incorrect behavior
39548 not ok 18 selftests: x86: syscall_numbering_64 # exit=1
details in attached kselftests-1b1f3b3e1b.xz
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: kselftests-1b1f3b3e1b.xz --]
[-- Type: application/x-xz, Size: 21196 bytes --]
reply other threads:[~2026-08-06 8:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608061019.b3aca16-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mkchauras@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ruanjinjie@huawei.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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.