From: kernel test robot <oliver.sang@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Anders Roxell <anders.roxell@linaro.org>,
Kees Cook <keescook@chromium.org>,
<linux-kselftest@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [broonie-misc:kselftest-seccomp-benchmark-ktap] [kselftest/seccomp] 626fa92237: kernel-selftests.seccomp.seccomp_benchmark.fail
Date: Tue, 6 Feb 2024 14:27:36 +0800 [thread overview]
Message-ID: <202402061002.3a8722fd-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.seccomp.seccomp_benchmark.fail" on:
commit: 626fa9223749db85f03678573dd49ba2c7b6cd8b ("kselftest/seccomp: Report each expectation we assert as a KTAP test")
https://git.kernel.org/cgit/linux/kernel/git/broonie/misc.git kselftest-seccomp-benchmark-ktap
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: group-s
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade 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/202402061002.3a8722fd-oliver.sang@intel.com
# timeout set to 120
# selftests: seccomp: seccomp_benchmark
# TAP version 13
# 1..7
# # Running on:
# # Linux lkp-csl-d01 6.8.0-rc1-00003-g626fa9223749 #1 SMP PREEMPT_DYNAMIC Wed Jan 31 08:33:40 CST 2024 x86_64 GNU/Linux
# # Current BPF sysctl settings:
# # /proc/sys/net/core/bpf_jit_enable:1
# # /proc/sys/net/core/bpf_jit_harden:0
# # Calibrating sample size for 15 seconds worth of syscalls ...
# # Benchmarking 36800370 syscalls...
# # 15.443201110 - 1.042366576 = 14400834534 (14.4s)
# # getpid native: 391 ns
# # 31.586833659 - 15.443583738 = 16143249921 (16.1s)
# # getpid RET_ALLOW 1 filter (bitmap): 438 ns
# # 47.494976754 - 31.587621280 = 15907355474 (15.9s)
# # getpid RET_ALLOW 2 filters (bitmap): 432 ns
# # 66.262898246 - 47.495560365 = 18767337881 (18.8s)
# # getpid RET_ALLOW 3 filters (full): 509 ns
# # 86.089613909 - 66.263287445 = 19826326464 (19.8s)
# # getpid RET_ALLOW 4 filters (full): 538 ns
# # Estimated total seccomp overhead for 1 bitmapped filter: 47 ns
# # Estimated total seccomp overhead for 2 bitmapped filters: 41 ns
# # Estimated total seccomp overhead for 3 full filters: 118 ns
# # Estimated total seccomp overhead for 4 full filters: 147 ns
# # Estimated seccomp entry overhead: 53 ns
# # Estimated seccomp per-filter overhead (last 2 diff): 29 ns
# # Estimated seccomp per-filter overhead (filters / 4): 23 ns
# # Expectations:
# # native ≤ 1 bitmap (391 ≤ 438): ✔️
# ok 1 native ≤ 1 bitmap
# # native ≤ 1 filter (391 ≤ 509): ✔️
# ok 2 native ≤ 1 filter
# # per-filter (last 2 diff) ≈ per-filter (filters / 4) (29 ≈ 23): ❌
# not ok 3 per-filter (last 2 diff) ≈ per-filter (filters / 4)
# # 1 bitmapped ≈ 2 bitmapped (47 ≈ 41): ❌
# not ok 4 1 bitmapped ≈ 2 bitmapped
# # Skipping constant action bitmap expectations: they appear unsupported.
# ok 5 # SKIP entry ≈ 1 bitmapped
# ok 6 # SKIP entry ≈ 2 bitmapped
# ok 7 # SKIP native + entry + (per filter * 4) ≈ 4 filters total
# # Saw unexpected benchmark result. Try running again with more samples?
# # Totals: pass:2 fail:2 xfail:0 xpass:0 skip:3 error:0
not ok 2 selftests: seccomp: seccomp_benchmark # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240206/202402061002.3a8722fd-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-06 6:27 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=202402061002.3a8722fd-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=anders.roxell@linaro.org \
--cc=broonie@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).