Re: LTP syscalls mseal02 and shmctl03 fails on compat mode 64-bit kernel on 32-bit rootfs

On Thu, 3 Jul 2025 at 19:47, Arnd Bergmann wrote: > > On Thu, Jul 3, 2025, at 15:47, Naresh Kamboju wrote: > > The LTP syscalls mseal02 and shmctl03 failed only with compat mode testing > > with 64-bit kernel with 32-bit rootfs combination. > > > > Would it be possi

LTP syscalls mseal02 and shmctl03 fails on compat mode 64-bit kernel on 32-bit rootfs

The LTP syscalls mseal02 and shmctl03 failed only with compat mode testing with 64-bit kernel with 32-bit rootfs combination. Would it be possible to detect compat mode test environment and handle the test expectation in LTP test development ? Test case: - ltp-syscalls/mseal02 - ltp-syscalls/sh

arm64: Kernel crash at devm_kmalloc include/linux/device.h: drivers/base/devres.c

Regression on arm64 FVP and rock-pi-4-b while booting the Linux next-20250312 and next-20250313. the following crash noticed with KVM Kconfigs. First seen on next-20250312. Good: next-20250311 Bad: 6.14.0-rc6-next-20250312 and 6.14.0-rc6-next-20250313 Boot regression: arm64 devm_kmalloc rk_iommu_

selftests: core: unshare_test: WARNING: at mm/util.c:671 __kvmalloc_node_noprof

The following kernel warning is noticed on all arch and all devices while running selftests: core: unshare_test on Linux next-20240823 and next-20240826. First seen on next-20240823. Good: next-20240822 BAD: next-20240823 and next-20240826 Reported-by: Linux Kernel Functional Testing Crash

next-20240715: WARNING: at kernel/cpu.c:527 lockdep_assert_cpus_held (kernel/cpu.c:527 (discriminator 7) kernel/cpu.c:516 (discriminator 7))

The following kernel warnings are noticed on today's Linux next-20240715 tag on the arm64 Raspberry Pi 4 Model B and x86_64 devices while booting. This is always reproducible: yes. GOOD: next-20240712 BAD: next-20240715 Reported-by: Linux Kernel Functional Testing Warning log: [0

selftests: arm64: fp-stress: KERNEL-1-0/3-0/4-0/6-0 - gcc-13 - Failed - clang-pass

The following selftests: arm64 tests failed on FVP-aemva test and kernel built with gcc-13 but pass with clang. arm64_fp-stress_KERNEL-1-0/3-0/4-0/6-0 - gcc-13 - Failed arm64_fp-stress_KERNEL-1-0/3-0/4-0/6-0 - clang-18 - Pass Reported-by: Linux Kernel Functional Testing Test log: - # ti

selftests: ftrace: WARNING: at arch/arm64/kernel/stacktrace.c:112 arch_stack_walk

The following kernel warning noticed on arm64 qemu-arm64 and rk3399-rock-pi-4 device while running selftests ftrace tests on Linux next-20240613. This is always reproducible on qemu-arm64 and rock-pi-4 device with kselftest merge configs Reported-by: Linux Kernel Functional Testing Test log: --

selftests: arm64: check_buffer_fill.c:94:93: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'char *' [-Wformat=]

The Linux next building selftests with clang and gcc-13 found these build warnings. Reported-by: Linux Kernel Functional Testing Build log: - PATH: Reported build warnings noticed on following test files, selftests/arm64/mte/ * check_buffer_fill.c * mte_common_util.c check_buffer_fill

selftests: arm64: sve-ptrace.c:85:40: warning: data argument not used by format string [-Wformat-extra-args]

The Linux next building selftests with clang-17 and gcc-13 found these build warnings. Reported-by: Linux Kernel Functional Testing Build log: - PATH: selftests/arm64/fp The reported build warnings noticed on following test files. * sve-ptrace.c * za-ptrace.c * zt-ptrace.c clang-1

selftests: resctrl: cat_test.c: In function 'noncont_cat_run_test': ../kselftest.h:74:9: error: impossible constraint in 'asm' 74 | __asm__ __volatile__ ("cpuid\n\t"

The Linux next building selftests with gcc-13 found these build warnings and errors. Reported-by: Linux Kernel Functional Testing Build log: - Path: selftests/resctrl/resctrl_tests/ In file included from resctrl.h:24, from cat_test.c:11: cat_test.c: In function 'noncont

selftests: mm: seal_elf.c:140:45: warning: format '%s' expects argument of type 'char *', but argument 5 has type 'char (*)[5]' [-Wformat=]

The Linux next building selftests with gcc-13 found these build warnings and errors. Reported-by: Linux Kernel Functional Testing Build log: - PATH: selftests/mm/seal_elf seal_elf.c: In function 'test_seal_elf': seal_elf.c:140:45: warning: format '%s' expects argument of type 'char *',

Re: [PATCH 00/14] Add support for suppressing warning backtraces

On Tue, 12 Mar 2024 at 22:33, Guenter Roeck wrote: > This series is based on the RFC patch and subsequent discussion at > https://patchwork.kernel.org/project/linux-kselftest/patch/02546e59-1afe-4b08-ba81-d94f3b691c9a@moroto.mountain/ > and offers a more comprehensive solution of the problem di

Re: [PATCH net-next] selftests/tc-testing: require an up to date iproute2 for blockcast tests

Hi Pedro, On Thu, 29 Feb 2024 at 20:08, Pedro Tammela wrote: > > Add the dependsOn test check for all the mirred blockcast tests. > It will prevent the issue reported by LKFT which happens when an older > iproute2 is used to run the current tdc. Thank you for the fix patch. LKFT tests run on Deb

Re: [PATCH net] selftests: net: ip_local_port_range: define IPPROTO_MPTCP

On Fri, 9 Feb 2024 at 19:27, Matthieu Baerts wrote: > > Hi Maxim, Naresh, > > On 09/02/2024 14:25, Maxim Galaganov wrote: > > Older glibc's netinet/in.h may leave IPPROTO_MPTCP undefined when > > building ip_local_port_range.c, that leads to "error: use of undeclared > > identifier 'IPPROTO_MPTCP'

selftests: net: ip_local_port_range.c:152:17: error: use of undeclared identifier 'IPPROTO_MPTCP'

I encountered the following build errors while compiling the selftests net test cases on Linux next-20240208 tag with clang toolchain. Reported-by: Linux Kernel Functional Testing selftests/net/ip_local_port_range ip_local_port_range.c:152:17: error: use of undeclared identifier 'IPPROTO_MPTCP'

lsm_list_modules_test.c:104:22: error: 'LSM_ID_IMA' undeclared (first use in this function); did you mean 'LSM_ID_YAMA'?

Following build errors noticed while building selftests lsm tests for x86 with gcc-13 toolchain on Linux next-20231127 tag. Build log: -- selftest/lsm/lsm_list_modules_test lsm_list_modules_test.c: In function 'correct_lsm_list_modules': lsm_list_modules_test.c:104:22: error: 'LSM_ID_IMA' unde

Re: selftests: gpio: crash on arm64

On Wed, 15 Nov 2023 at 07:12, wrote: > > Tue, Nov 07, 2023 at 07:21:32PM +0530, Naresh Kamboju kirjoitti: > > On Tue, 20 Jun 2023 at 22:11, Andy Shevchenko > > wrote: > > > On Tue, Apr 11, 2023 at 10:57:28AM +0200, Linus Walleij wrote: > > > > On Mon,

WARNING: CPU: 6 PID: 474 at include/linux/maple_tree.h:712 mmap_region (include/linux/maple_tree.h:556 include/linux/maple_tree.h:731

Following kernel panic noticed while running selftests: exec: load_address on Fastmodels (FVP) running Linux next-20231109. Reported-by: Linux Kernel Functional Testing log: --- # timeout set to 45 # selftests: exec: load_address_16777216 [ 238.405168] [ cut here ] [

selftests: memfd: run_fuse_test.sh - fuse_evict_inode - fs/fuse/inode.c:162 - panic

Following kernel panic noticed while running selftests: memfd: run_fuse_test.sh on arm64 Juno-r2 and x86 devices running Linux next-20231109. Reported-by: Linux Kernel Functional Testing log: --- # timeout set to 45 # selftests: memfd: run_fuse_test.sh # opening: ./mnt/memfd # fuse: DONE [ 1931.

Re: selftests: arm64: za-fork - ZA state invalid in child

On Tue, 7 Nov 2023 at 14:39, Naresh Kamboju wrote: > > Following selftests: arm64: za-fork test failures noticed on qemu-arm64. > But the same test passed on FVP and Juno-r2. > > Are we missing something on qemu-arm64 ? > qemu-system-arm installed at version: 8.1 The Qemu v

Re: selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address

Hi Mark, On Tue, 7 Nov 2023 at 21:37, Mark Brown wrote: > > On Tue, Nov 07, 2023 at 08:14:59PM +0530, Naresh Kamboju wrote: > > On Tue, 7 Nov 2023 at 19:51, Mark Brown wrote: > > > > This all seems very surprising, especially given that AFAICT there are > > >

Re: selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address

On Tue, 7 Nov 2023 at 19:51, Mark Brown wrote: > > On Tue, Nov 07, 2023 at 06:43:25PM +0530, Naresh Kamboju wrote: > > > # # SVE-VL-64-0: Expected > > [390439044000390480003904c0003904000139044001390480013904c0013904000239044002390480023904c00239040003390

Re: selftests: gpio: crash on arm64

Hi Linus and Bartosz, On Tue, 20 Jun 2023 at 22:11, Andy Shevchenko wrote: > > On Tue, Apr 11, 2023 at 10:57:28AM +0200, Linus Walleij wrote: > > On Mon, Apr 10, 2023 at 11:16 AM Naresh Kamboju > > wrote: > > ... > > > Add a pr_info() devm_gpio_chip_release()

selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address

Following kernel oops noticed while running kselftests arm64 on qemu-arm64 on stable-rc linux-6.6.y branch. I have re-built vmlinux with the same config and ran decode stackdump. Reported-by: Linux Kernel Functional Testing Logs: # selftests: arm64: fp-stress # TAP version 13 # 1..32 # # 2

Re: selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address

My apologies ! Please ignore this email. I will re-run for arm64 and get back to you. On Tue, 7 Nov 2023 at 18:32, Naresh Kamboju wrote: > > Following kernel oops noticed while running kselftests arm64 on qemu-arm64 > on stable-rc linux-6.6.y branch. > > I have re-built vmlinu

selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address

Following kernel oops noticed while running kselftests arm64 on qemu-arm64 on stable-rc linux-6.6.y branch. I have re-built vmlinux with the same config and ran decode stackdump. Reported-by: Linux Kernel Functional Testing Logs: # selftests: arm64: fp-stress # TAP version 13 # 1..32 # # 2

selftests: arm64: za-fork - ZA state invalid in child

Following selftests: arm64: za-fork test failures noticed on qemu-arm64. But the same test passed on FVP and Juno-r2. Are we missing something on qemu-arm64 ? qemu-system-arm installed at version: 8.1 host architecture: amd64 Started failing from Linux next-20231106 GOOD: next-20231103 Bad: next

Re: [PATCH v3 3/3] kselftest: Add new test for detecting unprobed Devicetree devices

Hi Aishwarya, On Thu, 2 Nov 2023 at 17:41, Aishwarya TCV wrote: > > > > On 28/08/2023 22:13, Nícolas F. R. A. Prado wrote: > > Introduce a new kselftest to detect devices that were declared in the > > Devicetree, and are expected to be probed by a driver, but weren't. > > > > The test uses two li

Re: [RFC] drm/tests: annotate intentional stack trace in drm_test_rect_calc_hscale()

On Mon, 30 Oct 2023 at 14:33, Dan Carpenter wrote: > > We have started printing more and more intentional stack traces. Whether > it's testing KASAN is able to detect use after frees or it's part of a > kunit test. > > These stack traces can be problematic. They suddenly show up as a new > failu

selftests: user_events: ftrace_test - RIP: 0010:tracing_update_buffers (kernel/trace/trace.c:6470)

Following kernel crash noticed on x86_64 while running selftests: user_events: ftrace_test running 6.6.0-rc7-next-20231026. Reported-by: Linux Kernel Functional Testing kselftest: Running tests in user_events TAP version 13 1..4 # timeout set to 90 # selftests: user_events: ftrace_test [ 2391.60

selftests: ftrace: RIP: 0010:__lock_acquire (kernel/locking/lockdep.c:5005)

Following kernel crash noticed on x86_64 while running selftests ftracetests running 6.6.0-rc7-next-20231026. Reported-by: Linux Kernel Functional Testing log: - # ok 44 ftrace - test for function traceon/off triggers # ok 45 ftrace - test tracing error log support # ok 46 Test creation and

Re: selftests: cgroup: test_core - Unable to handle kernel NULL pointer dereference at virtual address

On Sun, 8 Oct 2023 at 21:09, Roman Gushchin wrote: > > On Sun, Oct 08, 2023 at 11:30:52AM +0530, Naresh Kamboju wrote: > > While running selftests: cgroup: test_kmem on FVP following kernel crash > > noticed on Linux next 6.6.0-rc4-next-20231006. > > Hi Naresh! >

selftests: cgroup: test_core - Unable to handle kernel NULL pointer dereference at virtual address

While running selftests: cgroup: test_kmem on FVP following kernel crash noticed on Linux next 6.6.0-rc4-next-20231006. Reported-by: Linux Kernel Functional Testing Boot log: [0.00] Booting Linux on physical CPU 0x00 [0x410fd0f0] [0.00] Linux version 6.6.0-rc4-next-202310

Re: selftests: user_events: ftrace_test: Internal error: Oops: 0000000096000021

On Wed, 20 Sept 2023 at 16:21, Mark Rutland wrote: > > Hi Naresh, > > As a general thing, for arm64 issues could you please Cc the linux-arm-kernel > mailing list? > > On Wed, Sep 20, 2023 at 02:40:24PM +0200, Naresh Kamboju wrote: > > Following selftests: user_eve

selftests: user_events: ftrace_test: Internal error: Oops: 0000000096000021

Following selftests: user_events: ftrace_test running on arm64 Juno-r2 Linux next-20230919. Reported-by: Linux Kernel Functional Testing kselftest: Running tests in user_events TAP version 13 1..4 # timeout set to 90 # selftests: user_events: ftrace_test [ 1138.755735] Unable to handle kernel pa