- Linux-kselftest-mirror - lists.linaro.org

[GIT PULL] Kselftest fixes update for Linux 6.4-rc3

by Shuah Khan

Hi Linus, Please pull the following Kselftest fixes update for Linux 6.4-rc3. This Kselftest fixes update for Linux 6.4-rc3 consists of: - sgx test fix for false negatives. - ftrace output is hard to parse and it masks inappropriate skips etc. This fix addresses the problems by integrating with kselftest runner. diff is attached. thanks, -- Shuah ---------------------------------------------------------------- The following changes since commit ac9a78681b921877518763ba0e89202254349d1b: Linux 6.4-rc1 (2023-05-07 13:34:35 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux-kselftest-fixes-6.4-rc3 for you to fetch changes up to dbcf76390eb9a65d5d0c37b0cd57335218564e37: selftests/ftrace: Improve integration with kselftest runner (2023-05-08 11:10:13 -0600) ---------------------------------------------------------------- linux-kselftest-fixes-6.4-rc3 This Kselftest fixes update for Linux 6.4-rc3 consists of: - sgx test fix for false negatives. - ftrace output is hard to parse and it masks inappropriate skips etc. This fix addresses the problems by integrating with kselftest runner. ---------------------------------------------------------------- Mark Brown (1): selftests/ftrace: Improve integration with kselftest runner Yi Lai (1): selftests/sgx: Add "test_encl.elf" to TEST_FILES tools/testing/selftests/ftrace/Makefile | 3 +- tools/testing/selftests/ftrace/ftracetest | 63 ++++++++++++++++++++++++-- tools/testing/selftests/ftrace/ftracetest-ktap | 8 ++++ tools/testing/selftests/sgx/Makefile | 1 + 4 files changed, 71 insertions(+), 4 deletions(-) create mode 100755 tools/testing/selftests/ftrace/ftracetest-ktap ----------------------------------------------------------------

2 years, 6 months

2
1
0 0

[PATCH v2 0/2] KVM: s390: CMMA migration selftest and small bugfix

by Nico Boehr

v2: --- * swap order of patches (thanks Claudio) * add r-b * add comment why memslots are zeroed Add a new selftest for CMMA migration. Also fix a small issue found during development of the test. Nico Boehr (2): KVM: s390: fix KVM_S390_GET_CMMA_BITS for GFNs in memslot holes KVM: s390: selftests: add selftest for CMMA migration arch/s390/kvm/kvm-s390.c | 4 + tools/testing/selftests/kvm/Makefile | 1 + tools/testing/selftests/kvm/s390x/cmma_test.c | 680 ++++++++++++++++++ 3 files changed, 685 insertions(+) create mode 100644 tools/testing/selftests/kvm/s390x/cmma_test.c -- 2.39.1

2 years, 6 months

3
7
0 0

Re: [PATCH v2 8/9] eventfs: moving tracing/events to eventfs

by Ajay Kaher

> kernel test robot noticed "WARNING:at_fs/namei.c:#lookup_one_len" on: > > commit: 2fe2002efb23a715f5eb7a58891ff85f4e37b084 ("[PATCH v2 8/9] eventfs: moving tracing/events to eventfs") > url: https://github.com/intel-lab-lkp/linux/commits/Ajay-Kaher/eventfs-introduci… > base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git next > patch link: https://lore.kernel.org/all/1683026600-13485-9-git-send-email-akaher@vmware… > patch subject: [PATCH v2 8/9] eventfs: moving tracing/events to eventfs . . . > 49.752082][ T5878] eventfs_start_creating (fs/tracefs/inode.c:519) > [ 49.757416][ T5878] eventfs_create_dir (fs/tracefs/event_inode.c:187 (discriminator 3)) > [ 49.762488][ T5878] eventfs_root_lookup (fs/tracefs/event_inode.c:291) > [ 49.767637][ T5878] __lookup_slow (fs/namei.c:1686) > [ 49.772268][ T5878] walk_component (include/linux/fs.h:773 fs/namei.c:1704 fs/namei.c:1994) > [ 49.777016][ T5878] link_path_walk+0x24e/0x3b0 > [ 49.783462][ T5878] ? path_init (fs/namei.c:2387) > [ 49.788021][ T5878] path_openat (fs/namei.c:3711) > [ 49.792463][ T5878] do_filp_open (fs/namei.c:3742) > [ 49.797021][ T5878] ? __check_object_size (mm/memremap.c:107 mm/memremap.c:144) > [ 49.803055][ T5878] do_sys_openat2 (fs/open.c:1348) > [ 49.807740][ T5878] __x64_sys_openat (fs/open.c:1375) > [ 49.812512][ T5878] do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) > [ 49.817068][ T5878] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) > [ 49.823092][ T5878] RIP: 0033:0x7fcddb3b84e7 Steve, locally I have reproduced this issue using: lkp run job-cpu-100%-uprobe-60s.yaml And also fixed, I will include this fix as well in v3. Thanks to lkp, kernel test robot <yujie.liu(a)intel.com>. -Ajay

2 years, 6 months

2
1
0 0

[PATCH v1] selftests/bpf: Do not use sign-file as testcase

by Alexey Gladkov

The sign-file utility (from scripts/) is used in prog_tests/verify_pkcs7_sig.c, but the utility should not be called as a test. Executing this utility produces the following error: selftests: /linux/tools/testing/selftests/bpf: urandom_read ok 16 selftests: /linux/tools/testing/selftests/bpf: urandom_read selftests: /linux/tools/testing/selftests/bpf: sign-file not ok 17 selftests: /linux/tools/testing/selftests/bpf: sign-file # exit=2 Fixes: fc97590668ae ("selftests/bpf: Add test for bpf_verify_pkcs7_signature() kfunc") Signed-off-by: Alexey Gladkov <legion(a)kernel.org> --- tools/testing/selftests/bpf/Makefile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile index b677dcd0b77a..fd214d1526d4 100644 --- a/tools/testing/selftests/bpf/Makefile +++ b/tools/testing/selftests/bpf/Makefile @@ -88,8 +88,7 @@ TEST_GEN_PROGS_EXTENDED = test_sock_addr test_skb_cgroup_id_user \ xskxceiver xdp_redirect_multi xdp_synproxy veristat xdp_hw_metadata \ xdp_features -TEST_CUSTOM_PROGS = $(OUTPUT)/urandom_read $(OUTPUT)/sign-file -TEST_GEN_FILES += liburandom_read.so +TEST_GEN_FILES += liburandom_read.so urandom_read sign-file # Emit succinct information message describing current building step # $1 - generic step name (e.g., CC, LINK, etc); -- 2.33.7

2 years, 6 months

5
6
0 0

[PATCH net] net: selftests: Fix optstring

by Benjamin Poirier

The cited commit added a stray colon to the 'v' option. That makes the option work incorrectly. ex: tools/testing/selftests/net# ./fib_nexthops.sh -v (should enable verbose mode, instead it shows help text due to missing arg) Fixes: 5feba4727395 ("selftests: fib_nexthops: Make ping timeout configurable") Reviewed-by: Ido Schimmel <idosch(a)nvidia.com> Signed-off-by: Benjamin Poirier <bpoirier(a)nvidia.com> --- tools/testing/selftests/net/fib_nexthops.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/net/fib_nexthops.sh b/tools/testing/selftests/net/fib_nexthops.sh index a47b26ab48f2..0f5e88c8f4ff 100755 --- a/tools/testing/selftests/net/fib_nexthops.sh +++ b/tools/testing/selftests/net/fib_nexthops.sh @@ -2283,7 +2283,7 @@ EOF ################################################################################ # main -while getopts :t:pP46hv:w: o +while getopts :t:pP46hvw: o do case $o in t) TESTS=$OPTARG;; -- 2.40.1

2 years, 6 months

2
1
0 0

Re: [PATCH 6.1 000/239] 6.1.29-rc1 review

by Naresh Kamboju

On Mon, 15 May 2023 at 22:31, Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> wrote: > > This is the start of the stable review cycle for the 6.1.29 release. > There are 239 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed, 17 May 2023 16:16:37 +0000. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.29-rc1… > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. Regressions on arm64, arm, x86_64, and i386. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> We have recently upgraded our selftest sources to stable-rc 6.3 and running on stable rc 6.1 kernel. List of test regressions: ======== kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread kselftest-memfd - memfd_memfd_test kselftest-rseq - rseq_basic_test kselftest-kvm - kvm_hyperv_features - kvm_xapic_state_test ltp-commands - mkfs01_ntfs_sh Details: ===== # selftests: membarrier: membarrier_test_single_thread # TAP version 13 # 1..18 # Bail out! sys membarrier MEMBARRIER_CMD_GET_REGISTRATIONS test: flags = 0, errno = 22 # # Planned tests != run tests (18 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 1 selftests: membarrier: membarrier_test_single_thread # exit=1 # selftests: membarrier: membarrier_test_multi_thread # TAP version 13 # 1..16 # ok 1 sys_membarrier available # ok 2 sys membarrier invalid command test: command = -1, flags = 0, errno = 22. Failed as expected # ok 3 sys membarrier MEMBARRIER_CMD_QUERY invalid flags test: flags = 1, errno = 22. Failed as expected # ok 4 sys membarrier MEMBARRIER_CMD_PRIVATE_EXPEDITED not registered failure test: flags = 0, errno = 1 # ok 5 sys membarrier MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE not registered failure test: flags = 0, errno = 1 # ok 6 sys membarrier MEMBARRIER_CMD_GLOBAL test: flags = 0 # ok 7 sys membarrier MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED test: flags = 0 # Bail out! sys membarrier MEMBARRIER_CMD_GET_REGISTRATIONS test: flags = 0, errno = 22 # # Planned tests != run tests (16 != 7) # # Totals: pass:7 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: membarrier: membarrier_test_multi_thread # exit=1 ======== kselftest: Running tests in memfd TAP version 13 1..3 # selftests: memfd: memfd_test # Aborted not ok 1 selftests: memfd: memfd_test # exit=134 ======== kselftest: Running tests in rseq TAP version 13 1..9 # selftests: rseq: basic_test # basic_test: rseq.h:204: rseq_current_node_id: Assertion `rseq_node_id_available()' failed. # ./kselftest/runner.sh: line 35: 1709 Aborted /usr/bin/timeout --foreground \"$kselftest_timeout\" $1 not ok 1 selftests: rseq: basic_test # exit=134 # selftests: rseq: basic_percpu_ops_test # spinlock # percpu_list ok 2 selftests: rseq: basic_percpu_ops_test # selftests: rseq: basic_percpu_ops_mm_cid_test # spinlock # percpu_list ok 3 selftests: rseq: basic_percpu_ops_mm_cid_test # selftests: rseq: param_test ok 4 selftests: rseq: param_test # selftests: rseq: param_test_benchmark ok 5 selftests: rseq: param_test_benchmark # selftests: rseq: param_test_compare_twice ok 6 selftests: rseq: param_test_compare_twice # selftests: rseq: param_test_mm_cid # Error: cpu id getter unavailable not ok 7 selftests: rseq: param_test_mm_cid # exit=255 # selftests: rseq: param_test_mm_cid_benchmark # Error: cpu id getter unavailable not ok 8 selftests: rseq: param_test_mm_cid_benchmark # exit=255 # selftests: rseq: param_test_mm_cid_compare_twice # Error: cpu id getter unavailable not ok 9 selftests: rseq: param_test_mm_cid_compare_twice # exit=255 ====== # selftests: kvm: hyperv_features # Testing access to Hyper-V specific MSRs # ==== Test Assertion Failure ==== # x86_64/hyperv_features.c:498: false # pid=1043 tid=1043 errno=4 - Interrupted system call # 1 0x0000000000403722: ?? ??:0 # 2 0x00007fc1e890157a: ?? ??:0 # 3 0x00007fc1e890162f: ?? ??:0 # 4 0x00000000004037c4: ?? ??:0 # Failed guest assert: !vector at x86_64/hyperv_features.c:58 # MSR = 40000118, arg1 = d, arg2 = 0 not ok 10 selftests: kvm: hyperv_features # exit=254 # selftests: kvm: xapic_state_test # ==== Test Assertion Failure ==== # x86_64/xapic_state_test.c:147: apic_id == expected # pid=2175 tid=2175 errno=4 - Interrupted system call # 1 0x0000000000402bac: ?? ??:0 # 2 0x00000000004025ba: ?? ??:0 # 3 0x00007f0040cd457a: ?? ??:0 # 4 0x00007f0040cd462f: ?? ??:0 # 5 0x0000000000402624: ?? ??:0 # APIC_ID not set back to xAPIC format; wanted = 1000000, got = 1 not ok 46 selftests: kvm: xapic_state_test # exit=254 ==== tst_device.c:93:[ 147.226163] loop0: detected capacity change from 0 to 614400 TINFO: Found free device 0 '/dev/loop0' mkfs01 1 TINFO: timeout per run is 0h 50m 0s mkfs01 1 TPASS: 'mkfs -t ntfs /dev/loop0 ' passed. mkfs01 2 TINFO: Mounting device: mount -t ntfs /dev/loop0 /scratch/ltp-zKu0Zn6L6o/LTP_mkfs01.ULVi9nN6XF/mntpoint modprobe: FATAL: Module fuse not found in directory /lib/modules/6.2.16-rc1 ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root mkfs01 2 TBROK: Failed to mount device ntfs type: mount exit = 21 [ 166.420602] I/O error, dev loop0, sector 614272 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Steps to reproduce: ============ # To install tuxrun on your system globally: # sudo pip3 install -U tuxrun==0.42.0 # # See https://tuxrun.org/ for complete documentation. tuxrun \ --runtime podman \ --device qemu-x86_64 \ --boot-args rw \ --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2Pq4UnS1BCkrcnT51kVe… \ --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2Pq4UnS1BCkrcnT51kVe… \ --rootfs https://storage.tuxboot.com/debian/bookworm/amd64/rootfs.ext4.xz \ --parameters SKIPFILE=skipfile-lkft.yaml \ --parameters KSELFTEST=https://storage.tuxsuite.com/public/linaro/lkft/builds/2PeR5CFkuV… \ --image docker.io/lavasoftware/lava-dispatcher:2023.01.0020.gc1598238f \ --tests kselftest-membarrier \ --timeouts boot=15 Test log links and details, ========== membarrier: test_multi_thread: ========== - https://lkft.validation.linaro.org/scheduler/job/6427965#L1776 - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… memfd_test: ========= - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… rseq_basic_test: ========= - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… kvm: kvm_hyperv_features and kvm_xapic_state_test: ========= - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… ltp-commands: mkfs01_ntfs_sh: ======== - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… ## Build * kernel: 6.1.29-rc1 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.1.y * git commit: b82733c0ff99435bb7eb5ed4ea2e1c1fd69e7ebb * git describe: v6.1.28-240-gb82733c0ff99 * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.2… ## Test Regressions (compared to v6.1.28) * bcm2711-rpi-4-b, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * bcm2711-rpi-4-b, kselftest-memfd - memfd_memfd_test * dragonboard-410c, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * dragonboard-410c, kselftest-memfd - memfd_memfd_test * fvp-aemva, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * fvp-aemva, kselftest-memfd - memfd_memfd_test * i386, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * i386, kselftest-memfd - memfd_memfd_test * juno-r2, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * juno-r2, kselftest-memfd - memfd_memfd_test * qemu-arm64, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu-arm64, kselftest-memfd - memfd_memfd_test * qemu-armv7, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu-i386, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu-i386, kselftest-memfd - memfd_memfd_test * qemu-x86_64, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu-x86_64, kselftest-memfd - memfd_memfd_test * qemu_i386, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu_i386, kselftest-memfd - memfd_memfd_test * qemu_x86_64, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * qemu_x86_64, kselftest-memfd - memfd_memfd_test * x15, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * x15, kselftest-rseq - rseq_basic_test * x15, ltp-commands - mkfs01_ntfs_sh * x86, kselftest-kvm - kvm_hyperv_features - kvm_xapic_state_test * x86, kselftest-membarrier - membarrier_membarrier_test_multi_thread - membarrier_membarrier_test_single_thread * x86, kselftest-memfd - memfd_memfd_test * x86, kselftest-rseq - rseq_basic_test - rseq_run_param_test_sh * x86-kasan, ltp-commands - mkfs01_ntfs_sh ## Metric Regressions (compared to v6.1.28) ## Test Fixes (compared to v6.1.28) ## Metric Fixes (compared to v6.1.28) ## Test result summary total: 161145, pass: 139501, fail: 3428, skip: 17949, xfail: 267 ## Build Summary * arc: 5 total, 5 passed, 0 failed * arm: 151 total, 150 passed, 1 failed * arm64: 54 total, 53 passed, 1 failed * i386: 41 total, 38 passed, 3 failed * mips: 30 total, 28 passed, 2 failed * parisc: 8 total, 8 passed, 0 failed * powerpc: 38 total, 36 passed, 2 failed * riscv: 16 total, 15 passed, 1 failed * s390: 16 total, 16 passed, 0 failed * sh: 14 total, 12 passed, 2 failed * sparc: 8 total, 8 passed, 0 failed * x86_64: 46 total, 46 passed, 0 failed ## Test suites summary * boot * fwts * kselftest-android * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers-dma-buf * kselftest-efivarfs * kselftest-exec * kselftest-filesystems * kselftest-filesystems-binderfs * kselftest-firmware * kselftest-fpu * kselftest-ftrace * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net * kselftest-net-forwarding * kselftest-net-mptcp * kselftest-netfilter * kselftest-nsfs * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-user_events * kselftest-vDSO * kselftest-watchdog * kselftest-x86 * kselftest-zram * kunit * kvm-unit-tests * libhugetlbfs * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * perf * rcutorture * v4l2-compliance * vdso -- Linaro LKFT https://lkft.linaro.org

2 years, 6 months

1
0
0 0

[PATCH] HID: uclogic: Modular KUnit tests should not depend on KUNIT=y

by Geert Uytterhoeven

While KUnit tests that cannot be built as a loadable module must depend on "KUNIT=y", this is not true for modular tests, where it adds an unnecessary limitation. Fix this by relaxing the dependency to "KUNIT". Fixes: 08809e482a1c44d9 ("HID: uclogic: KUnit best practices and naming conventions") Signed-off-by: Geert Uytterhoeven <geert+renesas(a)glider.be> --- drivers/hid/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig index 4ce012f83253ec9f..b977450cac75265d 100644 --- a/drivers/hid/Kconfig +++ b/drivers/hid/Kconfig @@ -1285,7 +1285,7 @@ config HID_MCP2221 config HID_KUNIT_TEST tristate "KUnit tests for HID" if !KUNIT_ALL_TESTS - depends on KUNIT=y + depends on KUNIT depends on HID_BATTERY_STRENGTH depends on HID_UCLOGIC default KUNIT_ALL_TESTS -- 2.34.1

2 years, 6 months

3
2
0 0

selftests: mincore: mincore_selftest fails only on qemu-armv7

by Naresh Kamboju

The selftests: mincore: mincore_selftest fails only on qemu-armv7 running Linux next, mainline and stable branches. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> # selftests: mincore: mincore_selftest # TAP version 13 # 1..5 # # Starting 5 tests from 1 test cases. # # RUN global.basic_interface ... # # OK global.basic_interface # ok 1 global.basic_interface # # RUN global.check_anonymous_locked_pages ... # # OK global.check_anonymous_locked_pages # ok 2 global.check_anonymous_locked_pages # # RUN global.check_huge_pages ... # # mincore_selftest.c:156:check_huge_pages:mmap error: Invalid argument # # mincore_selftest.c:159:check_huge_pages:Expected 0 (0) == retval (-1) # # check_huge_pages: Test terminated by assertion # # FAIL global.check_huge_pages # not ok 3 global.check_huge_pages # # RUN global.check_file_mmap ... # # OK global.check_file_mmap # ok 4 global.check_file_mmap # # RUN global.check_tmpfs_mmap ... # # OK global.check_tmpfs_mmap # ok 5 global.check_tmpfs_mmap # # FAILED: 4 / 5 tests passed. # # Totals: pass:4 fail:1 xfail:0 xpass:0 skip:0 error:0 logs: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2PnaQ12zfS… History: https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-rc2/tes… Steps to reproduce: ---------------- # To install tuxrun on your system globally: # sudo pip3 install -U tuxrun==0.42.0 # # See https://tuxrun.org/ for complete documentation. tuxrun \ --runtime podman \ --device qemu-armv7 \ --boot-args rw \ --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaP3qqppMDr51qUdKv… \ --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaP3qqppMDr51qUdKv… \ --rootfs https://storage.tuxboot.com/debian/bookworm/armhf/rootfs.ext4.xz \ --parameters SKIPFILE=skipfile-lkft.yaml \ --parameters KSELFTEST=https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaP3qqpp… \ --image docker.io/lavasoftware/lava-dispatcher:2023.01.0020.gc1598238f \ --tests kselftest-mincore \ --timeouts boot=30 -- Linaro LKFT https://lkft.linaro.org

2 years, 6 months

4
3
0 0

selftests: x86: mov_ss_trap_64 numbering_64 amx_64 lam_64 failed

by Naresh Kamboju

Following selftests x86 test cases failing Unsupported feature can be marked as skipped instead of fail ? Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> - x86_mov_ss_trap_64 fail - x86_syscall_numbering_64 fail - x86_amx_64 fail - x86_lam_64 fail # selftests: x86: mov_ss_trap_64 # SS = 0x2b, &SS = 0x0x404188 # Set up a watchpoint # DR0 = 404188, DR1 = 401368, DR7 = 7000a # Segmentation fault not ok 10 selftests: x86: mov_ss_trap_64 # exit=139 # selftests: x86: syscall_numbering_64 ... not ok 16 selftests: x86: syscall_numbering_64 # TIMEOUT 45 seconds ## The default timeout after 45 seconds occurred due to slow qemu-x86_64 ## pass on x86 device and other fast qemu_x86_64. # selftests: x86: amx_64 # amx_64: [FAIL] cpuid: no CPU xsave support: Success not ok 18 selftests: x86: amx_64 # exit=1 # selftests: x86: lam_64 # # Unsupported LAM feature! not ok 19 selftests: x86: lam_64 # exit=255 links, - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-rc2/tes… - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-rc2/tes… Steps to reproduce: ------------ # To install tuxrun on your system globally: # sudo pip3 install -U tuxrun==0.42.0 # # See https://tuxrun.org/ for complete documentation. tuxrun \ --runtime podman \ --device qemu-x86_64 \ --boot-args rw \ --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaPptGlD8AJHQHUvVn… \ --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaPptGlD8AJHQHUvVn… \ --rootfs https://storage.tuxboot.com/debian/bookworm/amd64/rootfs.ext4.xz \ --parameters SKIPFILE=skipfile-lkft.yaml \ --parameters KSELFTEST=https://storage.tuxsuite.com/public/linaro/lkft/builds/2PnaPptGlD… \ --image docker.io/lavasoftware/lava-dispatcher:2023.01.0020.gc1598238f \ --tests kselftest-x86 \ --timeouts boot=15 -- Linaro LKFT https://lkft.linaro.org

2 years, 6 months

1
0
0 0

[PATCH 1/3] docs: admin-guide: add valsa driver documentation

by Ivan Orlov

Add documentation for the new Virtual ALSA driver. It covers all possible usage cases: errors and delay injections, random and pattern-based data generation, playback and ioctl redefinition functionalities testing. We have a lot of different virtual media drivers, which can be used for testing of the userspace applications and media subsystem middle layer. However, all of them are aimed at testing the video functionality and simulating the video devices. For audio devices we have only snd-dummy module, which is good in simulating the correct behavior of an ALSA device. I decided to write a tool, which would help to test the userspace ALSA programs (and the PCM middle layer as well) under unusual circumstances to figure out how they would behave. So I came up with this Virtual ALSA Driver. This new Virtual ALSA Driver has several features which can be useful during the userspace ALSA applications testing/fuzzing, or testing/fuzzing of the PCM middle layer. Not all of them can be implemented using the existing virtual drivers (like dummy or loopback). Here is what can this driver do: - Simulate both capture and playback processes - Check the playback stream for containing the looped pattern - Generate random or pattern-based capture data - Inject delays into the playback and capturing processes - Inject errors during the PCM callbacks Also, this driver can check the playback stream for containing the predefined pattern, which is used in the corresponding selftest to check the PCM middle layer data transferring functionality. Additionally, this driver redefines the default RESET ioctl, and the selftest covers this PCM API functionality as well. Signed-off-by: Ivan Orlov <ivan.orlov0322(a)gmail.com> --- Documentation/admin-guide/index.rst | 1 + Documentation/admin-guide/valsa.rst | 114 ++++++++++++++++++++++++++++ 2 files changed, 115 insertions(+) create mode 100644 Documentation/admin-guide/valsa.rst diff --git a/Documentation/admin-guide/index.rst b/Documentation/admin-guide/index.rst index 43ea35613dfc..328cc59275a1 100644 --- a/Documentation/admin-guide/index.rst +++ b/Documentation/admin-guide/index.rst @@ -131,6 +131,7 @@ configure specific aspects of kernel behavior to your liking. thunderbolt ufs unicode + valsa vga-softcursor video-output xfs diff --git a/Documentation/admin-guide/valsa.rst b/Documentation/admin-guide/valsa.rst new file mode 100644 index 000000000000..64ffc130fb4c --- /dev/null +++ b/Documentation/admin-guide/valsa.rst @@ -0,0 +1,114 @@ +.. SPDX-License-Identifier: GPL-2.0 + +The Virtual ALSA Driver +======================= + +The Virtual ALSA Driver emulates a generic ALSA device, and can be used for +testing/fuzzing of the userspace ALSA applications, as well as for testing/fuzzing of +the ALSA middle layer. Additionally, it can be used for simulating hard to reproduce +problems with PCM devices. + +What can this driver do? +~~~~~~~~~~~~~~~~~~~~~~~~ + +At this moment the driver can do the following things: + * Simulate both capture and playback processes + * Generate random or pattern-based capturing data + * Inject delays into the playback and capturing processes + * Inject errors during the PCM callbacks + +Also, this driver can check the playback stream for containing the +predefined pattern, which is used in the corresponding selftest (alsa/valsa-test.sh) +to check the PCM middle layer data transferring functionality. Additionally, this +driver redefines the default RESET ioctl, and the selftest covers this PCM +API functionality as well. + +Configuration +------------- + +The driver has several parameters besides the common ALSA module parameters: + + * fill_mode (bool) - Buffer fill mode (see below) + * inject_delay (int) + * inject_hwpars_err (bool) + * inject_prepare_err (bool) + * inject_trigger_err (bool) + + +Capture Data Generation +----------------------- + +The driver has two modes of data generation: the first (0 in the fill_mode parameter) +means random data generation, the second (1 in the fill_mode) - pattern-based +data generation. Let's look at the second mode. + +First of all, you may want to specify the pattern for data generation. You can do it +by writing the pattern to the debugfs file (/sys/kernel/debug/valsa/fill_pattern). +Like that: + +.. code-block:: bash + + echo -n mycoolpattern > /sys/kernel/debug/valsa/fill_pattern + +After this, every capture action performed on the 'valsa' device will return +'mycoolpatternmycoolpatternmycoolpatternmy...' in the capturing buffer. + +The pattern itself can be up to 4096 bytes long. + +Delay injection +--------------- + +The driver has 'inject_delay' parameter, which has very self-descriptive name and +can be used for time delay/speedup simulations. The parameter has integer type, and +it means the delay added between module's internal timer ticks. + +If the 'inject_delay' value is positive, the buffer will be filled slower, if it is +negative - faster. You can try it yourself by starting a recording in any +audiorecording application (like Audacity) and selecting the 'valsa' device as a +source. + +This parameter can be also used for generating a huge amount of sound data in a very +short period of time (with the negative 'inject_delay' value). + +Errors injection +---------------- + +This module can be used for injecting errors into the PCM communication process. This +action can help you to figure out how the userspace ALSA program behaves under unusual +circumstances. + +For example, you can make all 'hw_params' PCM callback calls return EBUSY error by +writing '1' to the 'inject_hwpars_err' module parameter: + +.. code-block:: bash + + echo 1 > /sys/module/snd_valsa/parameters/inject_hwpars_err + +Errors can be injected into the following PCM callbacks: + + * hw_params (EBUSY) + * prepare (EINVAL) + * trigger (EINVAL) + + +Playback test +------------- + +This driver can be also used for the playback functionality testing - every time you +write the playback data to the 'valsa' PCM device and close it, the driver checks the +buffer for containing the looped pattern (which is specified in the fill_pattern +debugfs file). If the playback buffer content represents the looped pattern, 'pc_test' +debugfs entry is set into '1'. Otherwise, the driver sets it to '0'. + +ioctl redefinition test +----------------------- + +The driver redefines the 'reset' ioctl, which is default for all PCM devices. To test +this functionality, we can trigger the reset ioctl and check the 'ioctl_test' debugfs +entry: + +.. code-block:: bash + + cat /sys/kernel/debug/valsa/ioctl_test + +If the ioctl is triggered successfully, this file will contain '1', and '0' otherwise. -- 2.34.1

2 years, 6 months

3
8
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-kselftest-mirror