Re: [PATCH bpf-next v3 8/9] bpf/tests: add tests for cpuv4 instructions
Hello,
kernel test robot noticed "kernel-selftests.net.test_bpf.sh.fail" on:
commit: 361ceaa10db461a35068f21db451a02c07e2a6bd ("[PATCH bpf-next v3 8/9]
bpf/tests: add tests for cpuv4 instructions")
url:
https://github.com/intel-lab-lkp/linux/commits/Puranjay-Mohan/arm32-bpf-add-support-for-32-bit-offset-jmp-instruction/20230908-070721
base: https://git.kernel.org/cgit/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/all/20230907230550.1417590-9-puranja...@gmail.com/
patch subject: [PATCH bpf-next v3 8/9] bpf/tests: add tests for cpuv4
instructions
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: net
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
| Closes:
https://lore.kernel.org/oe-lkp/202309261451.8934f9ad-oliver.s...@intel.com
# timeout set to 1500
# selftests: net: test_bpf.sh
# test_bpf: [FAIL]
not ok 13 selftests: net: test_bpf.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230926/202309261451.8934f9ad-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 4/4] kunit: test: Fix the possible memory leak in executor_test
Hi Jinjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc3 next-20230926]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/kunit-Fix-missed-memory-release-in-kunit_free_suite_set/20230922-151243
base: linus/master
patch link:
https://lore.kernel.org/r/20230922071020.2554677-5-ruanjinjie%40huawei.com
patch subject: [PATCH v3 4/4] kunit: test: Fix the possible memory leak in
executor_test
config: powerpc-allyesconfig
(https://download.01.org/0day-ci/archive/20230927/202309270433.wgmfrgjd-...@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git
4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20230927/202309270433.wgmfrgjd-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202309270433.wgmfrgjd-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from lib/kunit/executor.c:353:
>> lib/kunit/executor_test.c:278:4: warning: cast from 'void (*)(struct
>> kunit_suite_set *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts
>> to incompatible function type [-Wcast-function-type-strict]
278 | (kunit_action_t *)free_suite_set,
| ^~~~
1 warning generated.
vim +278 lib/kunit/executor_test.c
264
265 /* Use the resource API to register a call to free_suite_set.
266 * Since we never actually use the resource, it's safe to use on const
data.
267 */
268 static void free_suite_set_at_end(struct kunit *test, const void
*to_free)
269 {
270 if (!((struct kunit_suite_set *)to_free)->start)
271 return;
272
273 struct kunit_suite_set *free = kzalloc(sizeof(struct
kunit_suite_set),
274 GFP_KERNEL);
275 *free = *(struct kunit_suite_set *)to_free;
276
277 kunit_add_action(test,
> 278 (kunit_action_t *)free_suite_set,
279 (void *)free);
280 }
281
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 09/20] arm64: define VM_PKEY_BIT* for arm64
Hi Joey, kernel test robot noticed the following build errors: [auto build test ERROR on arm64/for-next/core] [also build test ERROR on linus/master v6.6-rc3 next-20230929] [cannot apply to akpm-mm/mm-everything kvmarm/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Joey-Gouly/arm64-sysreg-add-system-register-POR_EL-0-1/20230927-221459 base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core patch link: https://lore.kernel.org/r/20230927140123.5283-10-joey.gouly%40arm.com patch subject: [PATCH v1 09/20] arm64: define VM_PKEY_BIT* for arm64 config: arm64-randconfig-001-20230930 (https://download.01.org/0day-ci/archive/20230930/202309301944.jgh1qzvm-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230930/202309301944.jgh1qzvm-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202309301944.jgh1qzvm-...@intel.com/ All errors (new ones prefixed by >>): In file included from fs/proc/meminfo.c:5: arch/arm64/include/asm/mman.h: In function 'arch_calc_vm_prot_bits': >> include/linux/mm.h:346:25: error: 'VM_HIGH_ARCH_2' undeclared (first use in >> this function) 346 | # define VM_PKEY_BIT0 VM_HIGH_ARCH_2 /* A protection key is a 3-bit value on arm64 */ | ^~ arch/arm64/include/asm/mman.h:20:29: note: in expansion of macro 'VM_PKEY_BIT0' 20 | ret |= pkey & 0x1 ? VM_PKEY_BIT0 : 0; | ^~~~ include/linux/mm.h:346:25: note: each undeclared identifier is reported only once for each function it appears in 346 | # define VM_PKEY_BIT0 VM_HIGH_ARCH_2 /* A protection key is a 3-bit value on arm64 */ | ^~ arch/arm64/include/asm/mman.h:20:29: note: in expansion of macro 'VM_PKEY_BIT0' 20 | ret |= pkey & 0x1 ? VM_PKEY_BIT0 : 0; | ^~~~ >> include/linux/mm.h:347:25: error: 'VM_HIGH_ARCH_3' undeclared (first use in >> this function) 347 | # define VM_PKEY_BIT1 VM_HIGH_ARCH_3 | ^~ arch/arm64/include/asm/mman.h:21:29: note: in expansion of macro 'VM_PKEY_BIT1' 21 | ret |= pkey & 0x2 ? VM_PKEY_BIT1 : 0; | ^~~~ >> include/linux/mm.h:348:25: error: 'VM_HIGH_ARCH_4' undeclared (first use in >> this function) 348 | # define VM_PKEY_BIT2 VM_HIGH_ARCH_4 | ^~ arch/arm64/include/asm/mman.h:22:29: note: in expansion of macro 'VM_PKEY_BIT2' 22 | ret |= pkey & 0x4 ? VM_PKEY_BIT2 : 0; | ^~~~ vim +/VM_HIGH_ARCH_2 +346 include/linux/mm.h 343 344 #if defined(CONFIG_ARM64) 345 # define VM_PKEY_SHIFT VM_HIGH_ARCH_BIT_2 > 346 # define VM_PKEY_BIT0 VM_HIGH_ARCH_2 /* A protection key is a 3-bit > value on arm64 */ > 347 # define VM_PKEY_BIT1 VM_HIGH_ARCH_3 > 348 # define VM_PKEY_BIT2 VM_HIGH_ARCH_4 349 # define VM_PKEY_BIT3 0 350 # define VM_PKEY_BIT4 0 351 #endif 352 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 11/20] arm64: enable ARCH_HAS_PKEYS on arm64
Hi Joey, kernel test robot noticed the following build errors: [auto build test ERROR on arm64/for-next/core] [also build test ERROR on linus/master v6.6-rc3 next-20230929] [cannot apply to akpm-mm/mm-everything kvmarm/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Joey-Gouly/arm64-sysreg-add-system-register-POR_EL-0-1/20230927-221459 base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core patch link: https://lore.kernel.org/r/20230927140123.5283-12-joey.gouly%40arm.com patch subject: [PATCH v1 11/20] arm64: enable ARCH_HAS_PKEYS on arm64 config: arm64-randconfig-001-20230930 (https://download.01.org/0day-ci/archive/20230930/202309302050.so3qxukm-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230930/202309302050.so3qxukm-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202309302050.so3qxukm-...@intel.com/ All errors (new ones prefixed by >>): In file included from arch/arm64/include/asm/hwcap.h:50, from arch/arm64/include/asm/cpufeature.h:12, from arch/arm64/include/asm/ptrace.h:11, from arch/arm64/include/asm/irqflags.h:10, from include/linux/irqflags.h:17, from include/linux/spinlock.h:59, from include/linux/mmzone.h:8, from include/linux/gfp.h:7, from include/linux/mm.h:7, from include/linux/pagewalk.h:5, from fs/proc/task_mmu.c:2: fs/proc/task_mmu.c: In function 'show_smap_vma_flags': include/linux/mm.h:346:25: error: 'VM_HIGH_ARCH_2' undeclared (first use in this function) 346 | # define VM_PKEY_BIT0 VM_HIGH_ARCH_2 /* A protection key is a 3-bit value on arm64 */ | ^~ include/linux/log2.h:158:30: note: in definition of macro 'ilog2' 158 | __builtin_constant_p(n) ? \ | ^ fs/proc/task_mmu.c:689:24: note: in expansion of macro 'VM_PKEY_BIT0' 689 | [ilog2(VM_PKEY_BIT0)] = "", |^~~~ include/linux/mm.h:346:25: note: each undeclared identifier is reported only once for each function it appears in 346 | # define VM_PKEY_BIT0 VM_HIGH_ARCH_2 /* A protection key is a 3-bit value on arm64 */ | ^~ include/linux/log2.h:158:30: note: in definition of macro 'ilog2' 158 | __builtin_constant_p(n) ? \ | ^ fs/proc/task_mmu.c:689:24: note: in expansion of macro 'VM_PKEY_BIT0' 689 | [ilog2(VM_PKEY_BIT0)] = "", |^~~~ >> include/linux/log2.h:157:1: error: array index in initializer not of integer >> type 157 | ( \ | ^ fs/proc/task_mmu.c:689:18: note: in expansion of macro 'ilog2' 689 | [ilog2(VM_PKEY_BIT0)] = "", | ^ include/linux/log2.h:157:1: note: (near initialization for 'mnemonics') 157 | ( \ | ^ fs/proc/task_mmu.c:689:18: note: in expansion of macro 'ilog2' 689 | [ilog2(VM_PKEY_BIT0)] = "", | ^ include/linux/mm.h:347:25: error: 'VM_HIGH_ARCH_3' undeclared (first use in this function) 347 | # define VM_PKEY_BIT1 VM_HIGH_ARCH_3 | ^~ include/linux/log2.h:158:30: note: in definition of macro 'ilog2' 158 | __builtin_constant_p(n) ? \ | ^ fs/proc/task_mmu.c:690:24: note: in expansion of macro 'VM_PKEY_BIT1' 690 | [ilog2(VM_PKEY_BIT1)] = "", |^~~~ >> include/linux/log2.h:157:1: error: array index in initializer not of integer >> type 157 | ( \ | ^ fs/proc/task_mmu.c:690:18: note: in expansion of macro 'ilog2' 690 | [ilog2(VM_PKEY_BIT1)] = "", | ^ include/linux/log2.h:157:1: note: (near initialization for 'mnemonics') 157 | ( \ | ^ fs/proc/task_mmu.c:690:18: note: in expan
[linux-next:master] BUILD REGRESSION 7d730f1bf6f39ece2d9f3ae682f12e5b593d534d
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 7d730f1bf6f39ece2d9f3ae682f12e5b593d534d Add linux-next specific
files for 20231005
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202309122047.cri9yjrq-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202309192314.vbsjiim5-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202309212121.cul1ptra-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202309212339.hxhbu2f1-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202309221945.uwcq56zg-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202310041744.d34giv9v-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202310042215.w9pg3rqs-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202310051547.40nm4sif-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202310052201.anvbpgpr-...@intel.com
Error/Warning: (recently discovered and may have been fixed)
Documentation/gpu/amdgpu/thermal:43: ./drivers/gpu/drm/amd/pm/amdgpu_pm.c:988:
WARNING: Unexpected indentation.
arch/x86/include/asm/string_32.h:150:25: warning: '__builtin_memcpy' writing 3
bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
drivers/cpufreq/sti-cpufreq.c:215:50: warning: '%d' directive output may be
truncated writing between 1 and 10 bytes into a region of size 2
[-Wformat-truncation=]
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c:274: warning: Function parameter or
member 'gart_placement' not described in 'amdgpu_gmc_gart_location'
fs/bcachefs/bcachefs_format.h:215:25: warning: 'p' offset 3 in 'struct bkey'
isn't aligned to 4 [-Wpacked-not-aligned]
fs/bcachefs/bcachefs_format.h:217:25: warning: 'version' offset 27 in 'struct
bkey' isn't aligned to 4 [-Wpacked-not-aligned]
fs/gfs2/inode.c:1876:14: sparse:struct gfs2_glock *
fs/gfs2/inode.c:1876:14: sparse:struct gfs2_glock [noderef] __rcu *
fs/gfs2/super.c:1543:17: sparse:struct gfs2_glock *
fs/gfs2/super.c:1543:17: sparse:struct gfs2_glock [noderef] __rcu *
include/linux/fortify-string.h:57:33: warning: writing 8 bytes into a region of
size 0 [-Wstringop-overflow=]
kernel/bpf/helpers.c:1906:19: warning: no previous declaration for
'bpf_percpu_obj_new_impl' [-Wmissing-declarations]
kernel/bpf/helpers.c:1942:18: warning: no previous declaration for
'bpf_percpu_obj_drop_impl' [-Wmissing-declarations]
kernel/bpf/helpers.c:2477:18: warning: no previous declaration for 'bpf_throw'
[-Wmissing-declarations]
Unverified Error/Warning (likely false positive, please contact us if
interested):
Documentation/devicetree/bindings/mfd/qcom-pm8xxx.yaml:
arch/x86/kvm/x86.c:8891 x86_emulate_instruction() warn: missing error code? 'r'
drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c:209 amdgpu_mca_smu_get_mca_entry()
warn: variable dereferenced before check 'mca_funcs' (see line 200)
drivers/gpu/drm/i915/display/intel_psr.c:3185 i915_psr_sink_status_show()
error: uninitialized symbol 'error_status'.
drivers/gpu/drm/i915/display/intel_tc.c:327 mtl_tc_port_get_max_lane_count()
error: uninitialized symbol 'pin_mask'.
fs/exfat/namei.c:393 exfat_find_empty_entry() error: uninitialized symbol
'last_clu'.
fs/ntfs3/bitmap.c:663 wnd_init() warn: Please consider using kvcalloc instead
of kvmalloc_array
fs/ntfs3/super.c:466:23: sparse: sparse: unknown escape sequence: '\%'
lib/kunit/executor_test.c:39 parse_filter_test() error: double free of
'filter.suite_glob'
lib/kunit/executor_test.c:40 parse_filter_test() error: double free of
'filter.test_glob'
scripts/mod/modpost.c:1437:14: warning: passing 'typeof (rela->r_offset) *'
(aka 'const unsigned long *') to parameter of type 'void *' discards qualifiers
[-Wincompatible-pointer-types-discards-qualifiers]
scripts/mod/modpost.c:1440:11: warning: passing 'typeof (rela->r_addend) *'
(aka 'const long *') to parameter of type 'void *' discards qualifiers
[-Wincompatible-pointer-types-discards-qualifiers]
scripts/mod/modpost.c:1472:14: warning: passing 'typeof (rel->r_offset) *' (aka
'const unsigned long *') to parameter of type 'void *' discards qualifiers
[-Wincompatible-pointer-types-discards-qualifiers]
{standard input}:1127: Error: unknown .loc sub-directive `is_stm'
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
|-- arc-allmodconfig
| |--
drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location
| |--
fs-bcachefs-bcachefs_format.h:warning:p-offset-in-struct-bkey-isn-t-aligned-to
| `--
fs-bcachefs-bcachefs_format.h:warning:version-offset-in-struct-bkey-isn-t-aligned-to
|-- arc-allyesconfig
| |--
drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location
| |--
fs-bcachefs-bcachefs_format.h:warning:p-offset-in-struct-bkey-isn-t-aligned-to
| `--
fs-bcachefs-bcachefs_format.h:warning:version-offset-in-struct-bkey-isn-t-aligned-to
|-- arm-allmodconfig
| `--
drivers-cpu
[linux-next:master] BUILD REGRESSION c0a6edb636cba9c0d1db966a54d910a02e52e4be
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: c0a6edb636cba9c0d1db966a54d910a02e52e4be Add linux-next specific files for 20231010 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202309122047.cri9yjrq-...@intel.com https://lore.kernel.org/oe-kbuild-all/202309160053.sfdnniu4-...@intel.com https://lore.kernel.org/oe-kbuild-all/202309192314.vbsjiim5-...@intel.com https://lore.kernel.org/oe-kbuild-all/202309202345.yprvhw8q-...@intel.com https://lore.kernel.org/oe-kbuild-all/202309212121.cul1ptra-...@intel.com https://lore.kernel.org/oe-kbuild-all/202309212339.hxhbu2f1-...@intel.com https://lore.kernel.org/oe-kbuild-all/202310051547.40nm4sif-...@intel.com https://lore.kernel.org/oe-kbuild-all/202310100409.lrbaypmk-...@intel.com Error/Warning: (recently discovered and may have been fixed) drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c:274: warning: Function parameter or member 'gart_placement' not described in 'amdgpu_gmc_gart_location' fs/bcachefs/bcachefs_format.h:215:25: warning: 'p' offset 3 in 'struct bkey' isn't aligned to 4 [-Wpacked-not-aligned] fs/bcachefs/bcachefs_format.h:217:25: warning: 'version' offset 27 in 'struct bkey' isn't aligned to 4 [-Wpacked-not-aligned] fs/bcachefs/btree_key_cache.c:113:7: warning: result of comparison of constant 9223372036854775807 with expression of type 'u32' (aka 'unsigned int') is always true [-Wtautological-constant-out-of-range-compare] include/linux/fortify-string.h:57:33: warning: writing 8 bytes into a region of size 0 [-Wstringop-overflow=] kernel/bpf/helpers.c:1909:19: warning: no previous declaration for 'bpf_percpu_obj_new_impl' [-Wmissing-declarations] kernel/bpf/helpers.c:1945:18: warning: no previous declaration for 'bpf_percpu_obj_drop_impl' [-Wmissing-declarations] kernel/bpf/helpers.c:2480:18: warning: no previous declaration for 'bpf_throw' [-Wmissing-declarations] lib/kunit/kunit-test.c:565:25: warning: cast from 'void (*)(const void *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts to incompatible function type [-Wcast-function-type-strict] Unverified Error/Warning (likely false positive, please contact us if interested): arch/x86/kvm/x86.c:9016 x86_emulate_instruction() warn: missing error code? 'r' drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c:538:25-29: ERROR: aconnector is NULL but dereferenced. Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- arc-allmodconfig | |-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location | |-- fs-bcachefs-bcachefs_format.h:warning:p-offset-in-struct-bkey-isn-t-aligned-to | `-- fs-bcachefs-bcachefs_format.h:warning:version-offset-in-struct-bkey-isn-t-aligned-to |-- arc-allyesconfig | |-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location | |-- fs-bcachefs-bcachefs_format.h:warning:p-offset-in-struct-bkey-isn-t-aligned-to | `-- fs-bcachefs-bcachefs_format.h:warning:version-offset-in-struct-bkey-isn-t-aligned-to |-- arm-allmodconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- arm-allyesconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- arm64-allmodconfig | |-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location | `-- include-linux-fortify-string.h:warning:writing-bytes-into-a-region-of-size |-- arm64-allyesconfig | |-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location | `-- include-linux-fortify-string.h:warning:writing-bytes-into-a-region-of-size |-- csky-allmodconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- csky-allyesconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- i386-allmodconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- i386-allyesconfig | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- i386-randconfig-051-20231010 | `-- drivers-gpu-drm-amd-amdgpu-amdgpu_gmc.c:warning:Function-parameter-or-member-gart_placement-not-described-in-amdgpu_gmc_gart_location |-- loongarch-al
Re: [PATCH v3 2/3] userfaultfd: UFFDIO_MOVE uABI
Hi Suren, kernel test robot noticed the following build warnings: [auto build test WARNING on akpm-mm/mm-everything] [also build test WARNING on next-20231017] [cannot apply to linus/master v6.6-rc6] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Suren-Baghdasaryan/mm-rmap-support-move-to-different-root-anon_vma-in-folio_move_anon_rmap/20231009-144552 base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything patch link: https://lore.kernel.org/r/20231009064230.2952396-3-surenb%40google.com patch subject: [PATCH v3 2/3] userfaultfd: UFFDIO_MOVE uABI config: i386-randconfig-141-20231017 (https://download.01.org/0day-ci/archive/20231018/202310180338.ztpcyeck-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce: (https://download.01.org/0day-ci/archive/20231018/202310180338.ztpcyeck-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202310180338.ztpcyeck-...@intel.com/ smatch warnings: mm/userfaultfd.c:1380 remap_pages() warn: unsigned 'src_start + len - src_addr' is never less than zero. vim +1380 mm/userfaultfd.c 1195 1196 /** 1197 * remap_pages - remap arbitrary anonymous pages of an existing vma 1198 * @dst_start: start of the destination virtual memory range 1199 * @src_start: start of the source virtual memory range 1200 * @len: length of the virtual memory range 1201 * 1202 * remap_pages() remaps arbitrary anonymous pages atomically in zero 1203 * copy. It only works on non shared anonymous pages because those can 1204 * be relocated without generating non linear anon_vmas in the rmap 1205 * code. 1206 * 1207 * It provides a zero copy mechanism to handle userspace page faults. 1208 * The source vma pages should have mapcount == 1, which can be 1209 * enforced by using madvise(MADV_DONTFORK) on src vma. 1210 * 1211 * The thread receiving the page during the userland page fault 1212 * will receive the faulting page in the source vma through the network, 1213 * storage or any other I/O device (MADV_DONTFORK in the source vma 1214 * avoids remap_pages() to fail with -EBUSY if the process forks before 1215 * remap_pages() is called), then it will call remap_pages() to map the 1216 * page in the faulting address in the destination vma. 1217 * 1218 * This userfaultfd command works purely via pagetables, so it's the 1219 * most efficient way to move physical non shared anonymous pages 1220 * across different virtual addresses. Unlike mremap()/mmap()/munmap() 1221 * it does not create any new vmas. The mapping in the destination 1222 * address is atomic. 1223 * 1224 * It only works if the vma protection bits are identical from the 1225 * source and destination vma. 1226 * 1227 * It can remap non shared anonymous pages within the same vma too. 1228 * 1229 * If the source virtual memory range has any unmapped holes, or if 1230 * the destination virtual memory range is not a whole unmapped hole, 1231 * remap_pages() will fail respectively with -ENOENT or -EEXIST. This 1232 * provides a very strict behavior to avoid any chance of memory 1233 * corruption going unnoticed if there are userland race conditions. 1234 * Only one thread should resolve the userland page fault at any given 1235 * time for any given faulting address. This means that if two threads 1236 * try to both call remap_pages() on the same destination address at the 1237 * same time, the second thread will get an explicit error from this 1238 * command. 1239 * 1240 * The command retval will return "len" is successful. The command 1241 * however can be interrupted by fatal signals or errors. If 1242 * interrupted it will return the number of bytes successfully 1243 * remapped before the interruption if any, or the negative error if 1244 * none. It will never return zero. Either it will return an error or 1245 * an amount of bytes successfully moved. If the retval reports a 1246 * "short" remap, the remap_pages() command should be repeated by 1247 * userland with src+retval, dst+reval, len-retval if it wants to know 1248 * about the error that interrupted it. 1249 * 1250 * The UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES flag can be specified to 1251 * prevent -ENOENT errors to materialize if there are holes in the 1252 * source virtual range that is being remapped. The holes will be 1253 * accounted as successfully remapped in
Re: [PATCH] kunit: run test suites only after module initialization completes
Hi Marco, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.6-rc6 next-20231017] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Marco-Pagani/kunit-run-test-suites-only-after-module-initialization-completes/20231017-161611 base: linus/master patch link: https://lore.kernel.org/r/20231016203548.21993-1-marpagan%40redhat.com patch subject: [PATCH] kunit: run test suites only after module initialization completes config: csky-randconfig-002-20231018 (https://download.01.org/0day-ci/archive/20231018/202310181220.us7bvp16-...@intel.com/config) compiler: csky-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231018/202310181220.us7bvp16-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202310181220.us7bvp16-...@intel.com/ All errors (new ones prefixed by >>): In file included from arch/csky/include/asm/thread_info.h:9, from include/linux/thread_info.h:60, from include/asm-generic/preempt.h:5, from ./arch/csky/include/generated/asm/preempt.h:1, from include/linux/preempt.h:79, from include/linux/spinlock.h:56, from include/linux/kref.h:16, from include/kunit/test.h:22, from include/kunit/resource.h:12, from lib/kunit/test.c:9: lib/kunit/test.c: In function 'kunit_module_exit': >> arch/csky/include/asm/page.h:38:43: error: 'high_memory' undeclared (first >> use in this function) 38 | (void *)(kaddr) < high_memory) | ^~~ lib/kunit/test.c:772:34: note: in expansion of macro 'virt_addr_valid' 772 | if (!suite_set.start || !virt_addr_valid(suite_set.start)) | ^~~ arch/csky/include/asm/page.h:38:43: note: each undeclared identifier is reported only once for each function it appears in 38 | (void *)(kaddr) < high_memory) | ^~~ lib/kunit/test.c:772:34: note: in expansion of macro 'virt_addr_valid' 772 | if (!suite_set.start || !virt_addr_valid(suite_set.start)) | ^~~ vim +/high_memory +38 arch/csky/include/asm/page.h 013de2d6671d89 Guo Ren 2018-09-05 36 013de2d6671d89 Guo Ren 2018-09-05 37 #define virt_addr_valid(kaddr) ((void *)(kaddr) >= (void *)PAGE_OFFSET && \ 013de2d6671d89 Guo Ren 2018-09-05 @38 (void *)(kaddr) < high_memory) 013de2d6671d89 Guo Ren 2018-09-05 39 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] kunit: run test suites only after module initialization completes
Hi Marco, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.6-rc6 next-20231018] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Marco-Pagani/kunit-run-test-suites-only-after-module-initialization-completes/20231017-161611 base: linus/master patch link: https://lore.kernel.org/r/20231016203548.21993-1-marpagan%40redhat.com patch subject: [PATCH] kunit: run test suites only after module initialization completes config: arm-randconfig-004-20231019 (https://download.01.org/0day-ci/archive/20231019/202310190514.ukp3bs5q-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231019/202310190514.ukp3bs5q-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202310190514.ukp3bs5q-...@intel.com/ All errors (new ones prefixed by >>): In file included from arch/arm/include/asm/page.h:188, from arch/arm/include/asm/thread_info.h:14, from include/linux/thread_info.h:60, from include/asm-generic/preempt.h:5, from ./arch/arm/include/generated/asm/preempt.h:1, from include/linux/preempt.h:79, from include/linux/spinlock.h:56, from include/linux/kref.h:16, from include/kunit/test.h:22, from include/kunit/resource.h:12, from lib/kunit/test.c:9: lib/kunit/test.c: In function 'kunit_module_exit': >> arch/arm/include/asm/memory.h:391:116: error: 'high_memory' undeclared >> (first use in this function) 391 | #define virt_addr_valid(kaddr) (((unsigned long)(kaddr) >= PAGE_OFFSET && (unsigned long)(kaddr) < (unsigned long)high_memory) \ | ^~~ lib/kunit/test.c:772:34: note: in expansion of macro 'virt_addr_valid' 772 | if (!suite_set.start || !virt_addr_valid(suite_set.start)) | ^~~ arch/arm/include/asm/memory.h:391:116: note: each undeclared identifier is reported only once for each function it appears in 391 | #define virt_addr_valid(kaddr) (((unsigned long)(kaddr) >= PAGE_OFFSET && (unsigned long)(kaddr) < (unsigned long)high_memory) \ | ^~~ lib/kunit/test.c:772:34: note: in expansion of macro 'virt_addr_valid' 772 | if (!suite_set.start || !virt_addr_valid(suite_set.start)) | ^~~ vim +/high_memory +391 arch/arm/include/asm/memory.h 05944d74bc28ff include/asm-arm/memory.h Russell King 2006-11-30 389 e26a9e00afc482 arch/arm/include/asm/memory.h Russell King 2014-03-25 390 #define virt_to_page(kaddr)pfn_to_page(virt_to_pfn(kaddr)) efea3403d4b7c6 arch/arm/include/asm/memory.h Laura Abbott 2013-12-21 @391 #define virt_addr_valid(kaddr) (((unsigned long)(kaddr) >= PAGE_OFFSET && (unsigned long)(kaddr) < (unsigned long)high_memory) \ e26a9e00afc482 arch/arm/include/asm/memory.h Russell King 2014-03-25 392 && pfn_valid(virt_to_pfn(kaddr))) ^1da177e4c3f41 include/asm-arm/memory.h Linus Torvalds 2005-04-16 393 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [RFC PATCH 6/7] selftest: tun: Add tests for virtio-net hashing
hi, Akihiko Odaki,
sorry for sending again, the previous one has some problem that lost most
of CC part.
Hello,
kernel test robot noticed "kernel-selftests.net.make.fail" on:
commit: c04079dfb34c2f534f013408b12218c14b286b7d ("[RFC PATCH 6/7] selftest:
tun: Add tests for virtio-net hashing")
url:
https://github.com/intel-lab-lkp/linux/commits/Akihiko-Odaki/net-skbuff-Add-tun_vnet_hash-flag/20231008-133245
base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git
next
patch link:
https://lore.kernel.org/all/20231008052101.144422-7-akihiko.od...@daynix.com/
patch subject: [RFC PATCH 6/7] selftest: tun: Add tests for virtio-net hashing
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: net
test: fcnal-test.sh
atomic_test: ipv6_runtime
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
| Closes:
https://lore.kernel.org/oe-lkp/202310192236.fde97031-oliver.s...@intel.com
KERNEL SELFTESTS: linux_headers_dir is
/usr/src/linux-headers-x86_64-rhel-8.3-kselftests-c04079dfb34c2f534f013408b12218c14b286b7d
2023-10-14 17:54:16 mount --bind
/lib/modules/6.6.0-rc2-00023-gc04079dfb34c/kernel/lib
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-c04079dfb34c2f534f013408b12218c14b286b7d/lib
make: Entering directory
'/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-c04079dfb34c2f534f013408b12218c14b286b7d/tools/bpf/resolve_btfids'
...
gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/
-I../../../include/ -isystem
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-c04079dfb34c2f534f013408b12218c14b286b7d/usr/include
-I../ txtimestamp.c -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-c04079dfb34c2f534f013408b12218c14b286b7d/tools/testing/selftests/net/txtimestamp
reuseport_bpf.c: In function ‘attach_cbpf’:
reuseport_bpf.c:133:28: error: array type has incomplete element type ‘struct
sock_filter’
133 | struct sock_filter code[] = {
|^~~~
reuseport_bpf.c:139:29: error: ‘BPF_A’ undeclared (first use in this function);
did you mean ‘BPF_H’?
139 | { BPF_RET | BPF_A, 0, 0, 0 },
| ^
| BPF_H
reuseport_bpf.c:139:29: note: each undeclared identifier is reported only once
for each function it appears in
reuseport_bpf.c:141:16: error: variable ‘p’ has initializer but incomplete type
141 | struct sock_fprog p = {
|^~
reuseport_bpf.c:142:18: error: ‘struct sock_fprog’ has no member named ‘len’
142 | .len = ARRAY_SIZE(code),
| ^~~
In file included from reuseport_bpf.c:27:
../kselftest.h:56:25: warning: excess elements in struct initializer
56 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]))
| ^
reuseport_bpf.c:142:24: note: in expansion of macro ‘ARRAY_SIZE’
142 | .len = ARRAY_SIZE(code),
|^~
../kselftest.h:56:25: note: (near initialization for ‘p’)
56 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]))
| ^
reuseport_bpf.c:142:24: note: in expansion of macro ‘ARRAY_SIZE’
142 | .len = ARRAY_SIZE(code),
|^~
reuseport_bpf.c:143:18: error: ‘struct sock_fprog’ has no member named ‘filter’
143 | .filter = code,
| ^~
reuseport_bpf.c:143:27: warning: excess elements in struct initializer
143 | .filter = code,
| ^~~~
reuseport_bpf.c:143:27: note: (near initialization for ‘p’)
reuseport_bpf.c:141:27: error: storage size of ‘p’ isn’t known
141 | struct sock_fprog p = {
| ^
reuseport_bpf.c:141:27: warning: unused variable ‘p’ [-Wunused-variable]
reuseport_bpf.c:133:28: warning: unused variable ‘code’ [-Wunused-variable]
133 | struct sock_filter code[] = {
|^~~~
reuseport_bpf.c: In function ‘test_filter_no_reuseport’:
reuseport_bpf.c:346:28: error: array type has incomplete element type ‘struct
sock_filter’
346 | struct sock_filter ccode[] = {{ BPF_RET | BPF_A, 0, 0, 0 }};
|^
reuseport_bpf.c:346:51: error: ‘BPF_A’ undeclared (first use in this function);
did you mean ‘BPF_H’?
346 | struct sock_filter ccode[]
[linux-next:master] [selftests] 5b45a75377: kernel-selftests.uevent.uevent_filtering.fail
Hello,
kernel test robot noticed "kernel-selftests.uevent.uevent_filtering.fail" on:
commit: 5b45a753776be5d21cf395ec97e81c9187fbeaca ("selftests: uevent filtering:
fix return on error in uevent_listener")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 2030579113a1b1b5bfd7ff24c0852847836d8fd1]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: group-03
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)
we also noticed this issue does not always happen. as below, we saw 15 failures
out of 50 runs. however, parent keeps passing.
37013b557b7f39e6 5b45a753776be5d21cf395ec97e
---
fail:runs %reproductionfail:runs
| | |
:50 30% 15:50
kernel-selftests.uevent.uevent_filtering.fail
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
| Closes:
https://lore.kernel.org/oe-lkp/202310261454.46082aaa-oliver.s...@intel.com
TAP version 13
1..1
# timeout set to 300
# selftests: uevent: uevent_filtering
# TAP version 13
# 1..1
# # Starting 1 tests from 1 test cases.
# # RUN global.uevent_filtering ...
#
add@/devices/virtual/mem/fullACTION=addDEVPATH=/devices/virtual/mem/fullSUBSYSTEM=memSYNTH_UUID=0MAJOR=1MINOR=7DEVNAME=fullDEVMODE=0666SEQNUM=3532
#
add@/devices/virtual/mem/fullACTION=addDEVPATH=/devices/virtual/mem/fullSUBSYSTEM=memSYNTH_UUID=0MAJOR=1MINOR=7DEVNAME=fullDEVMODE=0666SEQNUM=3546
#
add@/devices/virtual/mem/fullACTION=addDEVPATH=/devices/virtual/mem/fullSUBSYSTEM=memSYNTH_UUID=0MAJOR=1MINOR=7DEVNAME=fullDEVMODE=0666SEQNUM=3556
#
add@/devices/virtual/mem/fullACTION=addDEVPATH=/devices/virtual/mem/fullSUBSYSTEM=memSYNTH_UUID=0MAJOR=1MINOR=7DEVNAME=fullDEVMODE=0666SEQNUM=3585
#
add@/devices/virtual/mem/fullACTION=addDEVPATH=/devices/virtual/mem/fullSUBSYSTEM=memSYNTH_UUID=0MAJOR=1MINOR=7DEVNAME=fullDEVMODE=0666SEQNUM=3595
# No buffer space available - Failed to receive uevent
# # uevent_filtering.c:479:uevent_filtering:Expected 0 (0) == ret (-1)
# # uevent_filtering: Test failed at step #10
# # FAIL global.uevent_filtering
# not ok 1 global.uevent_filtering
# # FAILED: 0 / 1 tests passed.
# # Totals: pass:0 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 1 selftests: uevent: uevent_filtering # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231026/202310261454.46082aaa-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linux-next:master] [ptp] 403376ddb4: stress-ng.clock.ops_per_sec -12.7% regression
Hello,
kernel test robot noticed a -12.7% regression of stress-ng.clock.ops_per_sec on:
commit: 403376ddb4221be9db5326ae334773807df71ffe ("ptp: add debugfs interface
to see applied channel masks")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
testcase: stress-ng
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz
(Cascade Lake) with 128G memory
parameters:
nr_threads: 1
disk: 1HDD
testtime: 60s
class: interrupt
test: clock
cpufreq_governor: performance
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
| Closes:
https://lore.kernel.org/oe-lkp/202310271441.b9fb0896-oliver.s...@intel.com
Details are as below:
-->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231027/202310271441.b9fb0896-oliver.s...@intel.com
=
class/compiler/cpufreq_governor/disk/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
interrupt/gcc-12/performance/1HDD/x86_64-rhel-8.3/1/debian-11.1-x86_64-20220510.cgz/lkp-csl-d02/clock/stress-ng/60s
commit:
c5a445b1e9 ("ptp: support event queue reader channel masks")
403376ddb4 ("ptp: add debugfs interface to see applied channel masks")
c5a445b1e9347b14 403376ddb4221be9db5326ae334
---
%stddev %change %stddev
\ |\
2.50+8.3% 2.71iostat.cpu.system
0.05 ± 3% +0.00.06mpstat.cpu.all.soft%
1.84+0.22.04mpstat.cpu.all.sys%
200469 -10.7% 178950vmstat.system.cs
135153-7.8% 124597vmstat.system.in
2804514 -12.7%2448917stress-ng.clock.ops
46741 -12.7% 40815stress-ng.clock.ops_per_sec
78.00+2.6% 80.00
stress-ng.time.percent_of_cpu_this_job_got
5606454 -12.7%4896355
stress-ng.time.voluntary_context_switches
18583 ± 5% +31.1% 24360 ± 9% turbostat.C1
2.90 ± 2% +0.13.03turbostat.C1E%
5353747 -13.0%4655189turbostat.POLL
0.28-0.00.24turbostat.POLL%
10.11+1.4% 10.25turbostat.RAMWatt
88825-6.6% 82944proc-vmstat.nr_active_anon
11367+4.6% 11892proc-vmstat.nr_mapped
96532-6.6% 90119proc-vmstat.nr_shmem
19819+4.1% 20633proc-vmstat.nr_slab_reclaimable
88825-6.6% 82944proc-vmstat.nr_zone_active_anon
420661 +27.6% 536903 ± 35% proc-vmstat.numa_hit
420556 +27.4% 535725 ± 36% proc-vmstat.numa_local
133275-6.9% 124053proc-vmstat.pgactivate
488366 ± 2% +60.4% 783374proc-vmstat.pgalloc_normal
227687+3.2% 234860proc-vmstat.pgfault
323139 ± 3% +94.6% 628694proc-vmstat.pgfree
0.00 ±141%+325.0% 0.01 ± 26%
perf-sched.sch_delay.avg.ms.kjournald2.kthread.ret_from_fork.ret_from_fork_asm
0.01 ±217%+455.3% 0.04 ± 68%
perf-sched.sch_delay.max.ms.__cond_resched.__kmem_cache_alloc_node.__kmalloc_node.alloc_cpumask_var_node.clock_was_set
0.10 ± 14% +66.8% 0.16 ± 15%
perf-sched.sch_delay.max.ms.do_nanosleep.hrtimer_nanosleep.common_nsleep_timens.__x64_sys_clock_nanosleep
0.00 ±141%+325.0% 0.01 ± 26%
perf-sched.sch_delay.max.ms.kjournald2.kthread.ret_from_fork.ret_from_fork_asm
0.91 ± 21% -53.8% 0.42 ± 55%
perf-sched.sch_delay.max.ms.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
1.27 +18.7% 1.51
perf-sched.total_wait_and_delay.average.ms
1.27 +18.7% 1.51
perf-sched.total_wait_time.average.ms
18.82 ± 20% +59.4% 29.99 ± 27%
perf-sched.wait_and_delay.avg.ms.__cond_resched.generic_perform_write.shmem_file_write_iter.vfs_write.ksys_write
1278 ± 2% +16.3% 1487 ± 3%
perf-sched.wait_and_delay.count.smpboot_thread_fn.kthread.ret_from_fork.ret_from_fork_asm
220.33 ± 5% +14.1% 251.33 ± 2%
perf-sched.wait_and_delay.count.worker_thread.kthread.ret_from_fork.ret_from_fork_asm
0.20 ± 13% +63.7% 0.33 ± 14%
perf-sched.wait_and_delay.max.ms.do_nanosleep.hrtimer_nanosleep.common_nsleep_timens.__x64_sys_clock_nanosleep
18.82 ± 20%
Re: [PATCH v4 2/5] userfaultfd: UFFDIO_MOVE uABI
Hi Suren, kernel test robot noticed the following build warnings: [auto build test WARNING on akpm-mm/mm-everything] [also build test WARNING on next-20231027] [cannot apply to linus/master v6.6-rc7] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Suren-Baghdasaryan/mm-rmap-support-move-to-different-root-anon_vma-in-folio_move_anon_rmap/20231028-084120 base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything patch link: https://lore.kernel.org/r/20231028003819.652322-3-surenb%40google.com patch subject: [PATCH v4 2/5] userfaultfd: UFFDIO_MOVE uABI config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231028/202310281500.latmtbjs-...@intel.com/config) compiler: m68k-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231028/202310281500.latmtbjs-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202310281500.latmtbjs-...@intel.com/ All warnings (new ones prefixed by >>): >> mm/userfaultfd.c:1289: warning: Function parameter or member 'ctx' not >> described in 'move_pages' >> mm/userfaultfd.c:1289: warning: Function parameter or member 'mm' not >> described in 'move_pages' >> mm/userfaultfd.c:1289: warning: Function parameter or member 'mode' not >> described in 'move_pages' vim +1289 mm/userfaultfd.c 1211 1212 /** 1213 * move_pages - move arbitrary anonymous pages of an existing vma 1214 * @dst_start: start of the destination virtual memory range 1215 * @src_start: start of the source virtual memory range 1216 * @len: length of the virtual memory range 1217 * 1218 * Must be called with mmap_lock held for read. 1219 * 1220 * move_pages() remaps arbitrary anonymous pages atomically in zero 1221 * copy. It only works on non shared anonymous pages because those can 1222 * be relocated without generating non linear anon_vmas in the rmap 1223 * code. 1224 * 1225 * It provides a zero copy mechanism to handle userspace page faults. 1226 * The source vma pages should have mapcount == 1, which can be 1227 * enforced by using madvise(MADV_DONTFORK) on src vma. 1228 * 1229 * The thread receiving the page during the userland page fault 1230 * will receive the faulting page in the source vma through the network, 1231 * storage or any other I/O device (MADV_DONTFORK in the source vma 1232 * avoids move_pages() to fail with -EBUSY if the process forks before 1233 * move_pages() is called), then it will call move_pages() to map the 1234 * page in the faulting address in the destination vma. 1235 * 1236 * This userfaultfd command works purely via pagetables, so it's the 1237 * most efficient way to move physical non shared anonymous pages 1238 * across different virtual addresses. Unlike mremap()/mmap()/munmap() 1239 * it does not create any new vmas. The mapping in the destination 1240 * address is atomic. 1241 * 1242 * It only works if the vma protection bits are identical from the 1243 * source and destination vma. 1244 * 1245 * It can remap non shared anonymous pages within the same vma too. 1246 * 1247 * If the source virtual memory range has any unmapped holes, or if 1248 * the destination virtual memory range is not a whole unmapped hole, 1249 * move_pages() will fail respectively with -ENOENT or -EEXIST. This 1250 * provides a very strict behavior to avoid any chance of memory 1251 * corruption going unnoticed if there are userland race conditions. 1252 * Only one thread should resolve the userland page fault at any given 1253 * time for any given faulting address. This means that if two threads 1254 * try to both call move_pages() on the same destination address at the 1255 * same time, the second thread will get an explicit error from this 1256 * command. 1257 * 1258 * The command retval will return "len" is successful. The command 1259 * however can be interrupted by fatal signals or errors. If 1260 * interrupted it will return the number of bytes successfully 1261 * remapped before the interruption if any, or the negative error if 1262 * none. It will never return zero. Either it will return an error or 1263 * an amount of bytes successfully moved. If the retval reports a 1264 * "short" remap, the move_pages() command should be repeated by 1265 * user
Re: [PATCH v12] exec: Fix dead-lock in de_thread with ptrace_attach
Hi Bernd,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kees/for-next/execve]
[also build test WARNING on kees/for-next/seccomp shuah-kselftest/next
shuah-kselftest/fixes linus/master v6.6]
[cannot apply to next-20231030]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Bernd-Edlinger/exec-Fix-dead-lock-in-de_thread-with-ptrace_attach/20231030-133021
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
for-next/execve
patch link:
https://lore.kernel.org/r/AS8P193MB1285DF698D7524EDE22ABFA1E4A1A%40AS8P193MB1285.EURP193.PROD.OUTLOOK.COM
patch subject: [PATCH v12] exec: Fix dead-lock in de_thread with ptrace_attach
config: loongarch-randconfig-002-20231030
(https://download.01.org/0day-ci/archive/20231030/202310301604.k866zrj8-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231030/202310301604.k866zrj8-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202310301604.k866zrj8-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/cred.c:443: warning: duplicate section name 'Return'
vim +/Return +443 kernel/cred.c
435
436 /**
437 * is_dumpability_changed - Will changing creds from old to new
438 * affect the dumpability in commit_creds?
439 *
440 * Return: false - dumpability will not be changed in commit_creds.
441 * Return: true - dumpability will be changed to non-dumpable.
442 *
> 443 * @old: The old credentials
444 * @new: The new credentials
445 */
446 bool is_dumpability_changed(const struct cred *old, const struct cred
*new)
447 {
448 if (!uid_eq(old->euid, new->euid) ||
449 !gid_eq(old->egid, new->egid) ||
450 !uid_eq(old->fsuid, new->fsuid) ||
451 !gid_eq(old->fsgid, new->fsgid) ||
452 !cred_cap_issubset(old, new))
453 return true;
454
455 return false;
456 }
457
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] Kunit to check the longest symbol length
Hi Sergio, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.6 next-20231106] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Sergio-Gonz-lez-Collado/Kunit-to-check-the-longest-symbol-length/20231106-024653 base: linus/master patch link: https://lore.kernel.org/r/20231105184010.49194-1-sergio.collado%40gmail.com patch subject: [PATCH] Kunit to check the longest symbol length config: i386-randconfig-014-20231106 (https://download.01.org/0day-ci/archive/20231107/202311070705.7afwz7q4-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231107/202311070705.7afwz7q4-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202311070705.7afwz7q4-...@intel.com/ All errors (new ones prefixed by >>): >> arch/x86/tools/insn_decoder_test: error: malformed line 1810458: 7ng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7g1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] Kunit to check the longest symbol length
Hi Sergio, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on v6.6 next-20231107] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Sergio-Gonz-lez-Collado/Kunit-to-check-the-longest-symbol-length/20231106-024653 base: linus/master patch link: https://lore.kernel.org/r/20231105184010.49194-1-sergio.collado%40gmail.com patch subject: [PATCH] Kunit to check the longest symbol length config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20231108/202311080319.fcep5dtc-...@intel.com/config) compiler: sparc64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231108/202311080319.fcep5dtc-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202311080319.fcep5dtc-...@intel.com/ All warnings (new ones prefixed by >>): >> lib/longest_symbol_kunit.c:16:18: warning: no previous prototype for >> 'sg1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7g1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7ng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7g1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7n' >> [-Wmissing-prototypes] 16 | #define DI(name) s##name##name | ^ lib/longest_symbol_kunit.c:17:19: note: in expansion of macro 'DI' 17 | #define DDI(name) DI(n##name##name) | ^~ lib/longest_symbol_kunit.c:18:20: note: in expansion of macro 'DDI' 18 | #define DDDI(name) DDI(n##name##name) |^~~ lib/longest_symbol_kunit.c:19:21: note: in expansion of macro 'DDDI' 19 | #define I(name) DDDI(n##name##name) | ^~~~ lib/longest_symbol_kunit.c:20:22: note: in expansion of macro 'I' 20 | #define DI(name) I(n##name##name) | ^ lib/longest_symbol_kunit.c:25:27: note: in expansion of macro 'DI' 25 | #define LONGEST_SYM_NAME DI(g1h2i3j4k5l6m7n) | ^~ lib/longest_symbol_kunit.c:33:14: note: in expansion of macro 'LONGEST_SYM_NAME' 33 | noinline int LONGEST_SYM_NAME(void) | ^~~~ In file included from : lib/longest_symbol_kunit.c:16:18: warning: no previous prototype for 'sg1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7g1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7ng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7g1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7ne' [-Wmissing-prototypes] 16 | #define DI(name) s##name##name | ^ include/linux/compiler_types.h:83:23: note: in definition of macro '___PASTE' 83 | #define ___PASTE(a,b) a##b | ^ lib/longest_symbol_kunit.c:22:21: note: in expansion of macro '__PASTE' 22 | #define PLUS1(name) __PASTE(name, e) | ^~~ lib/longest_symbol_kunit.c:28:32: note: in expansion of macro 'PLUS1' 28 | #define LONGEST_SYM_NAME_PLUS1 PLUS1(LONGEST_SYM_NAME) |^ lib/longest_symbol_kunit.c:17:19: note: in expansion of macro 'DI' 17 | #define DDI(name) DI(n##name##name) | ^~ lib/longest_symbol_kunit.c:18:20: note: in expansion of macro 'DDI' 18 | #define DDDI(name) DDI(n##name##name) |^~~ lib/longest_symbol_kunit.c:19:21: note: in expansion of macro 'DDDI' 19 | #define I(name) DDDI(n##name##name) | ^~~~ lib/longest_symbol_kunit.c:20:22: note: in expansion of macro 'I' 20 | #define DI(name) I(n##name##name) | ^ lib/longest_symbol_kunit.c:25:27:
Re: [PATCH v3 1/5] workqueue: Make workqueue_set_unbound_cpumask() static
Hi Waiman,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.7-rc1]
[cannot apply to tj-cgroup/for-next tj-wq/for-next next-20231115]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Waiman-Long/workqueue-Make-workqueue_set_unbound_cpumask-static/20231116-010940
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:
https://lore.kernel.org/r/20231115170359.163299-2-longman%40redhat.com
patch subject: [PATCH v3 1/5] workqueue: Make workqueue_set_unbound_cpumask()
static
config: i386-tinyconfig
(https://download.01.org/0day-ci/archive/20231116/202311160353.fadfqwo3-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231116/202311160353.fadfqwo3-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202311160353.fadfqwo3-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/workqueue.c:4421:13: warning: 'apply_wqattrs_unlock' defined but not
>> used [-Wunused-function]
4421 | static void apply_wqattrs_unlock(void)
| ^~~~
>> kernel/workqueue.c:4414:13: warning: 'apply_wqattrs_lock' defined but not
>> used [-Wunused-function]
4414 | static void apply_wqattrs_lock(void)
| ^~
vim +/apply_wqattrs_unlock +4421 kernel/workqueue.c
8864b4e59f7945 Tejun Heo 2013-03-12 4413
a0111cf6710bd1 Lai Jiangshan 2015-05-19 @4414 static void
apply_wqattrs_lock(void)
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4415 {
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4416 /* CPUs should
stay stable across pwq creations and installations */
ffd8bea81fbb5a Sebastian Andrzej Siewior 2021-08-03 4417
cpus_read_lock();
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4418
mutex_lock(&wq_pool_mutex);
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4419 }
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4420
a0111cf6710bd1 Lai Jiangshan 2015-05-19 @4421 static void
apply_wqattrs_unlock(void)
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4422 {
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4423
mutex_unlock(&wq_pool_mutex);
ffd8bea81fbb5a Sebastian Andrzej Siewior 2021-08-03 4424
cpus_read_unlock();
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4425 }
a0111cf6710bd1 Lai Jiangshan 2015-05-19 4426
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests
Hi Nikolai, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on v6.7-rc2 next-20231121] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Nikolai-Kondrashov/MAINTAINERS-Introduce-V-field-for-required-tests/20231116-015419 base: linus/master patch link: https://lore.kernel.org/r/20231115175146.9848-2-Nikolai.Kondrashov%40redhat.com patch subject: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests reproduce: (https://download.01.org/0day-ci/archive/20231122/202311220843.vh7wyxdf-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202311220843.vh7wyxdf-...@intel.com/ All warnings (new ones prefixed by >>): >> Documentation/process/tests.rst: WARNING: document isn't included in any >> toctree -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 3/3] selftests/seccomp: Test seccomp filter load and attach
Hello,
kernel test robot noticed "kernel-selftests.seccomp.seccomp_bpf.fail" on:
commit: 95084d9b2b5f0b593724819288f3cb4e2c585cb0 ("[PATCH v3 3/3]
selftests/seccomp: Test seccomp filter load and attach")
url:
https://github.com/intel-lab-lkp/linux/commits/Hengqi-Chen/seccomp-Introduce-SECCOMP_LOAD_FILTER-operation/20231129-134337
base: https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git
for-next/seccomp
patch link:
https://lore.kernel.org/all/20231129053440.41522-4-hengqi.c...@gmail.com/
patch subject: [PATCH v3 3/3] selftests/seccomp: Test seccomp filter load and
attach
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
| Closes:
https://lore.kernel.org/oe-lkp/202312051652.ecd5fbc7-oliver.s...@intel.com
we noticed one test added in this commit can pass, but another will fail.
# # RUN global.seccomp_filter_load_and_attach ...
# #OK global.seccomp_filter_load_and_attach
# ok 56 global.seccomp_filter_load_and_attach
# # RUN global.seccomp_attach_fd_failed ...
# # seccomp_bpf.c:4792:seccomp_attach_fd_failed:Expected errno (22) == EFAULT
(14)
# # seccomp_attach_fd_failed: Test terminated by assertion
# # FAIL global.seccomp_attach_fd_failed
# not ok 57 global.seccomp_attach_fd_failed
...
# # FAILED: 97 / 98 tests passed.
# # Totals: pass:97 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 1 selftests: seccomp: seccomp_bpf # exit=1
we applied the patch set upon 31c65705a8cfa like below:
95084d9b2b5f0
(linux-review/Hengqi-Chen/seccomp-Introduce-SECCOMP_LOAD_FILTER-operation/20231129-134337)
selftests/seccomp: Test seccomp filter load and attach
8fcda1c36e519 seccomp: Introduce new flag SECCOMP_FILTER_FLAG_FILTER_FD
bd86f21cfe1e0 seccomp: Introduce SECCOMP_LOAD_FILTER operation
31c65705a8cfa (kees/for-next/seccomp, kees/for-linus/seccomp) perf/benchmark:
fix seccomp_unotify benchmark for 32-bit
ce9ecca0238b1 (tag: v6.6-rc2, hyperv/hyperv-next) Linux 6.6-rc2
not sure if this is the correct base, or is there any other dependency to run
new test seccomp_attach_fd_failed?
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231205/202312051652.ecd5fbc7-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] kunit: Add APIs for managing devices
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c8613be119892ccceffbc550b9b9d7d68b995c9e]
url:
https://github.com/intel-lab-lkp/linux/commits/davidgow-google-com/kunit-Add-APIs-for-managing-devices/20231205-153349
base: c8613be119892ccceffbc550b9b9d7d68b995c9e
patch link:
https://lore.kernel.org/r/20231205-kunit_bus-v1-1-635036d3bc13%40google.com
patch subject: [PATCH 1/4] kunit: Add APIs for managing devices
config: powerpc-randconfig-r081-20231205
(https://download.01.org/0day-ci/archive/20231205/202312052114.vqd1viy5-...@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git
4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231205/202312052114.vqd1viy5-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312052114.vqd1viy5-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/kunit/device.c:100:22: warning: no previous prototype for function
>> '__kunit_device_register_internal' [-Wmissing-prototypes]
100 | struct kunit_device *__kunit_device_register_internal(struct kunit
*test,
| ^
lib/kunit/device.c:100:1: note: declare 'static' if the function is not
intended to be used outside of this translation unit
100 | struct kunit_device *__kunit_device_register_internal(struct kunit
*test,
| ^
| static
1 warning generated.
vim +/__kunit_device_register_internal +100 lib/kunit/device.c
99
> 100 struct kunit_device *__kunit_device_register_internal(struct kunit
> *test,
101const char *name,
102struct
device_driver *drv)
103 {
104 struct kunit_device *kunit_dev;
105 int err = -ENOMEM;
106
107 kunit_dev = kzalloc(sizeof(struct kunit_device), GFP_KERNEL);
108 if (!kunit_dev)
109 return ERR_PTR(err);
110
111 kunit_dev->owner = test;
112
113 err = dev_set_name(&kunit_dev->dev, "%s.%s", test->name, name);
114 if (err) {
115 kfree(kunit_dev);
116 return ERR_PTR(err);
117 }
118
119 /* Set the expected driver pointer, so we match. */
120 kunit_dev->driver = drv;
121
122 kunit_dev->dev.release = kunit_device_release;
123 kunit_dev->dev.bus = &kunit_bus_type;
124 kunit_dev->dev.parent = &kunit_bus;
125
126 err = device_register(&kunit_dev->dev);
127 if (err) {
128 put_device(&kunit_dev->dev);
129 return ERR_PTR(err);
130 }
131
132 kunit_add_action(test, device_unregister_wrapper,
&kunit_dev->dev);
133
134 return kunit_dev;
135 }
136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] kunit: Add APIs for managing devices
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c8613be119892ccceffbc550b9b9d7d68b995c9e]
url:
https://github.com/intel-lab-lkp/linux/commits/davidgow-google-com/kunit-Add-APIs-for-managing-devices/20231205-153349
base: c8613be119892ccceffbc550b9b9d7d68b995c9e
patch link:
https://lore.kernel.org/r/20231205-kunit_bus-v1-1-635036d3bc13%40google.com
patch subject: [PATCH 1/4] kunit: Add APIs for managing devices
config: i386-randconfig-141-20231205
(https://download.01.org/0day-ci/archive/20231205/202312052230.ic1pg0uo-...@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231205/202312052230.ic1pg0uo-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312052230.ic1pg0uo-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/kunit/device.c:100:22: warning: no previous prototype for
>> '__kunit_device_register_internal' [-Wmissing-prototypes]
100 | struct kunit_device *__kunit_device_register_internal(struct kunit
*test,
| ^~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for DRM_I915_DEBUG_GEM
Depends on [n]: HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] &&
DRM_I915_WERROR [=n]
Selected by [m]:
- DRM_I915_DEBUG [=y] && HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] &&
!COMPILE_TEST [=n]
vim +/__kunit_device_register_internal +100 lib/kunit/device.c
99
> 100 struct kunit_device *__kunit_device_register_internal(struct kunit
> *test,
101const char *name,
102struct
device_driver *drv)
103 {
104 struct kunit_device *kunit_dev;
105 int err = -ENOMEM;
106
107 kunit_dev = kzalloc(sizeof(struct kunit_device), GFP_KERNEL);
108 if (!kunit_dev)
109 return ERR_PTR(err);
110
111 kunit_dev->owner = test;
112
113 err = dev_set_name(&kunit_dev->dev, "%s.%s", test->name, name);
114 if (err) {
115 kfree(kunit_dev);
116 return ERR_PTR(err);
117 }
118
119 /* Set the expected driver pointer, so we match. */
120 kunit_dev->driver = drv;
121
122 kunit_dev->dev.release = kunit_device_release;
123 kunit_dev->dev.bus = &kunit_bus_type;
124 kunit_dev->dev.parent = &kunit_bus;
125
126 err = device_register(&kunit_dev->dev);
127 if (err) {
128 put_device(&kunit_dev->dev);
129 return ERR_PTR(err);
130 }
131
132 kunit_add_action(test, device_unregister_wrapper,
&kunit_dev->dev);
133
134 return kunit_dev;
135 }
136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] kunit: Add APIs for managing devices
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c8613be119892ccceffbc550b9b9d7d68b995c9e]
url:
https://github.com/intel-lab-lkp/linux/commits/davidgow-google-com/kunit-Add-APIs-for-managing-devices/20231205-153349
base: c8613be119892ccceffbc550b9b9d7d68b995c9e
patch link:
https://lore.kernel.org/r/20231205-kunit_bus-v1-1-635036d3bc13%40google.com
patch subject: [PATCH 1/4] kunit: Add APIs for managing devices
config: x86_64-randconfig-122-20231205
(https://download.01.org/0day-ci/archive/20231205/202312052210.igxjp7wu-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231205/202312052210.igxjp7wu-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312052210.igxjp7wu-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/kunit/device.c:100:21: sparse: sparse: symbol
>> '__kunit_device_register_internal' was not declared. Should it be static?
vim +/__kunit_device_register_internal +100 lib/kunit/device.c
99
> 100 struct kunit_device *__kunit_device_register_internal(struct kunit
> *test,
101const char *name,
102struct
device_driver *drv)
103 {
104 struct kunit_device *kunit_dev;
105 int err = -ENOMEM;
106
107 kunit_dev = kzalloc(sizeof(struct kunit_device), GFP_KERNEL);
108 if (!kunit_dev)
109 return ERR_PTR(err);
110
111 kunit_dev->owner = test;
112
113 err = dev_set_name(&kunit_dev->dev, "%s.%s", test->name, name);
114 if (err) {
115 kfree(kunit_dev);
116 return ERR_PTR(err);
117 }
118
119 /* Set the expected driver pointer, so we match. */
120 kunit_dev->driver = drv;
121
122 kunit_dev->dev.release = kunit_device_release;
123 kunit_dev->dev.bus = &kunit_bus_type;
124 kunit_dev->dev.parent = &kunit_bus;
125
126 err = device_register(&kunit_dev->dev);
127 if (err) {
128 put_device(&kunit_dev->dev);
129 return ERR_PTR(err);
130 }
131
132 kunit_add_action(test, device_unregister_wrapper,
&kunit_dev->dev);
133
134 return kunit_dev;
135 }
136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] kunit: Add APIs for managing devices
Hi, kernel test robot noticed the following build errors: [auto build test ERROR on c8613be119892ccceffbc550b9b9d7d68b995c9e] url: https://github.com/intel-lab-lkp/linux/commits/davidgow-google-com/kunit-Add-APIs-for-managing-devices/20231205-153349 base: c8613be119892ccceffbc550b9b9d7d68b995c9e patch link: https://lore.kernel.org/r/20231205-kunit_bus-v1-1-635036d3bc13%40google.com patch subject: [PATCH 1/4] kunit: Add APIs for managing devices config: x86_64-buildonly-randconfig-001-20231205 (https://download.01.org/0day-ci/archive/20231205/202312052341.feujgbbc-...@intel.com/config) compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231205/202312052341.feujgbbc-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202312052341.feujgbbc-...@intel.com/ All errors (new ones prefixed by >>): ld: lib/kunit/device.o: in function `kunit_bus_init': >> device.c:(.text+0x40): multiple definition of `init_module'; >> lib/kunit/test.o:test.c:(.init.text+0x0): first defined here -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm/tests: Switch to kunit devices
Hi Maxime, kernel test robot noticed the following build errors: [auto build test ERROR on next-20231205] [cannot apply to drm-misc/drm-misc-next v6.7-rc4 v6.7-rc3 v6.7-rc2 linus/master v6.7-rc4] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Maxime-Ripard/drm-tests-Switch-to-kunit-devices/20231205-170508 base: next-20231205 patch link: https://lore.kernel.org/r/20231205090405.153140-1-mripard%40kernel.org patch subject: [PATCH] drm/tests: Switch to kunit devices config: i386-buildonly-randconfig-004-20231206 (https://download.01.org/0day-ci/archive/20231207/202312070011.fdjyhkoz-...@intel.com/config) compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231207/202312070011.fdjyhkoz-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202312070011.fdjyhkoz-...@intel.com/ All errors (new ones prefixed by >>): >> drivers/gpu/drm/tests/drm_kunit_helpers.c:8:10: fatal error: >> 'kunit/device.h' file not found #include ^~~~ 1 error generated. vim +8 drivers/gpu/drm/tests/drm_kunit_helpers.c 7 > 8 #include 9 #include 10 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm/tests: Switch to kunit devices
Hi Maxime, kernel test robot noticed the following build errors: [auto build test ERROR on next-20231205] [cannot apply to drm-misc/drm-misc-next v6.7-rc4 v6.7-rc3 v6.7-rc2 linus/master v6.7-rc4] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Maxime-Ripard/drm-tests-Switch-to-kunit-devices/20231205-170508 base: next-20231205 patch link: https://lore.kernel.org/r/20231205090405.153140-1-mripard%40kernel.org patch subject: [PATCH] drm/tests: Switch to kunit devices config: i386-randconfig-012-20231206 (https://download.01.org/0day-ci/archive/20231207/202312070010.hafmuyfe-...@intel.com/config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231207/202312070010.hafmuyfe-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202312070010.hafmuyfe-...@intel.com/ All errors (new ones prefixed by >>): >> drivers/gpu/drm/tests/drm_kunit_helpers.c:8:10: fatal error: kunit/device.h: >> No such file or directory #include ^~~~ compilation terminated. vim +8 drivers/gpu/drm/tests/drm_kunit_helpers.c 7 > 8 #include 9 #include 10 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [net-next v1 06/16] netdev: support binding dma-buf to netdevice
Hi Mina,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/net-page_pool-factor-out-releasing-DMA-from-releasing-the-page/20231208-085531
base: net-next/main
patch link:
https://lore.kernel.org/r/20231208005250.2910004-7-almasrymina%40google.com
patch subject: [net-next v1 06/16] netdev: support binding dma-buf to netdevice
config: m68k-randconfig-r071-20231208
(https://download.01.org/0day-ci/archive/20231208/202312082303.bcpecr0q-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231208/202312082303.bcpecr0q-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312082303.bcpecr0q-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:22,
from arch/m68k/include/asm/bug.h:32,
from include/linux/bug.h:5,
from include/linux/thread_info.h:13,
from include/asm-generic/preempt.h:5,
from ./arch/m68k/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from arch/m68k/include/asm/irqflags.h:6,
from include/linux/irqflags.h:17,
from arch/m68k/include/asm/atomic.h:6,
from include/linux/atomic.h:7,
from include/linux/rcupdate.h:25,
from include/linux/rculist.h:11,
from include/linux/pid.h:5,
from include/linux/sched.h:14,
from include/linux/uaccess.h:8,
from net/core/dev.c:71:
net/core/dev.c: In function '__netdev_dmabuf_binding_free':
>> net/core/dev.c:2071:34: warning: format '%lu' expects argument of type 'long
>> unsigned int', but argument 2 has type 'size_t' {aka 'unsigned int'}
>> [-Wformat=]
2071 | if (!WARN(size != avail, "can't destroy genpool. size=%lu,
avail=%lu",
|
^~~~
2072 | size, avail))
|
| |
| size_t {aka unsigned int}
include/linux/printk.h:427:25: note: in definition of macro
'printk_index_wrap'
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~
include/linux/printk.h:129:17: note: in expansion of macro 'printk'
129 | printk(fmt, ##__VA_ARGS__); \
| ^~
include/asm-generic/bug.h:176:9: note: in expansion of macro 'no_printk'
176 | no_printk(format);
\
| ^
net/core/dev.c:2071:14: note: in expansion of macro 'WARN'
2071 | if (!WARN(size != avail, "can't destroy genpool. size=%lu,
avail=%lu",
| ^~~~
net/core/dev.c:2071:65: note: format string is defined here
2071 | if (!WARN(size != avail, "can't destroy genpool. size=%lu,
avail=%lu",
| ~~^
| |
| long
unsigned int
| %u
net/core/dev.c:2071:34: warning: format '%lu' expects argument of type 'long
unsigned int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
2071 | if (!WARN(size != avail, "can't destroy genpool. size=%lu,
avail=%lu",
|
^~~~
2072 | size, avail))
| ~
| |
| size_t {aka unsigned int}
include/linux/printk.h:427:25: note: in definition of macro
'printk_index_wrap'
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~
include/linux/printk.h:129:17: note: in expansion of macro 'printk'
129 | printk(fmt, ##__VA_ARGS__); \
| ^~
include/asm-generic/bug.h:176:9: note: in expansi
Re: [net-next v1 13/16] tcp: RX path for devmem TCP
Hi Mina,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/net-page_pool-factor-out-releasing-DMA-from-releasing-the-page/20231208-085531
base: net-next/main
patch link:
https://lore.kernel.org/r/20231208005250.2910004-14-almasrymina%40google.com
patch subject: [net-next v1 13/16] tcp: RX path for devmem TCP
config: alpha-defconfig
(https://download.01.org/0day-ci/archive/20231208/202312082353.lfkttexo-...@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231208/202312082353.lfkttexo-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312082353.lfkttexo-...@intel.com/
All errors (new ones prefixed by >>):
net/ipv4/tcp.c: In function 'tcp_recvmsg_dmabuf':
>> net/ipv4/tcp.c:2348:57: error: 'SO_DEVMEM_LINEAR' undeclared (first use in
>> this function)
2348 | err = put_cmsg(msg, SOL_SOCKET,
SO_DEVMEM_LINEAR,
|
^~~~
net/ipv4/tcp.c:2348:57: note: each undeclared identifier is reported only
once for each function it appears in
>> net/ipv4/tcp.c:2411:48: error: 'SO_DEVMEM_DMABUF' undeclared (first use in
>> this function)
2411 |SO_DEVMEM_DMABUF,
|^~~~
vim +/SO_DEVMEM_LINEAR +2348 net/ipv4/tcp.c
2306
2307 /* On error, returns the -errno. On success, returns number of bytes
sent to the
2308 * user. May not consume all of @remaining_len.
2309 */
2310 static int tcp_recvmsg_dmabuf(const struct sock *sk, const struct
sk_buff *skb,
2311unsigned int offset, struct msghdr *msg,
2312int remaining_len)
2313 {
2314 struct dmabuf_cmsg dmabuf_cmsg = { 0 };
2315 unsigned int start;
2316 int i, copy, n;
2317 int sent = 0;
2318 int err = 0;
2319
2320 do {
2321 start = skb_headlen(skb);
2322
2323 if (!skb->dmabuf) {
2324 err = -ENODEV;
2325 goto out;
2326 }
2327
2328 /* Copy header. */
2329 copy = start - offset;
2330 if (copy > 0) {
2331 copy = min(copy, remaining_len);
2332
2333 n = copy_to_iter(skb->data + offset, copy,
2334 &msg->msg_iter);
2335 if (n != copy) {
2336 err = -EFAULT;
2337 goto out;
2338 }
2339
2340 offset += copy;
2341 remaining_len -= copy;
2342
2343 /* First a dmabuf_cmsg for # bytes copied to
user
2344 * buffer.
2345 */
2346 memset(&dmabuf_cmsg, 0, sizeof(dmabuf_cmsg));
2347 dmabuf_cmsg.frag_size = copy;
> 2348 err = put_cmsg(msg, SOL_SOCKET,
> SO_DEVMEM_LINEAR,
2349 sizeof(dmabuf_cmsg),
&dmabuf_cmsg);
2350 if (err || msg->msg_flags & MSG_CTRUNC) {
2351 msg->msg_flags &= ~MSG_CTRUNC;
2352 if (!err)
2353 err = -ETOOSMALL;
2354 goto out;
2355 }
2356
2357 sent += copy;
2358
2359 if (remaining_len == 0)
2360 goto out;
2361 }
2362
2363 /* after that, send information of dmabuf pages through
a
2364 * sequence of cmsg
2365 */
2366 for (i = 0; i < skb_shinfo(skb)->nr_frags; i++) {
2367 skb_frag_t *frag = &skb_shinfo(skb)->frags[i];
2368 struct page_pool_iov *ppiov;
2369 u64 frag_offset;
2370 u32 user_token;
2371 int end;
2372
2373 /* skb->dmabuf should indicate that ALL the
frags in
2374
Re: [net-next v1 06/16] netdev: support binding dma-buf to netdevice
Hi Mina,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/net-page_pool-factor-out-releasing-DMA-from-releasing-the-page/20231208-085531
base: net-next/main
patch link:
https://lore.kernel.org/r/20231208005250.2910004-7-almasrymina%40google.com
patch subject: [net-next v1 06/16] netdev: support binding dma-buf to netdevice
config: i386-randconfig-141-20231208
(https://download.01.org/0day-ci/archive/20231208/202312082305.dmh51qvo-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231208/202312082305.dmh51qvo-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202312082305.dmh51qvo-...@intel.com/
All warnings (new ones prefixed by >>):
>> net/core/dev.c:2072:5: warning: format specifies type 'unsigned long' but
>> the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
size, avail))
^~~~
include/asm-generic/bug.h:134:29: note: expanded from macro 'WARN'
__WARN_printf(TAINT_WARN, format); \
^~
include/asm-generic/bug.h:106:17: note: expanded from macro '__WARN_printf'
__warn_printk(arg); \
^~~
net/core/dev.c:2072:11: warning: format specifies type 'unsigned long' but
the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
size, avail))
^
include/asm-generic/bug.h:134:29: note: expanded from macro 'WARN'
__WARN_printf(TAINT_WARN, format); \
^~
include/asm-generic/bug.h:106:17: note: expanded from macro '__WARN_printf'
__warn_printk(arg); \
^~~
net/core/dev.c:4356:1: warning: unused function 'sch_handle_ingress'
[-Wunused-function]
sch_handle_ingress(struct sk_buff *skb, struct packet_type **pt_prev, int
*ret,
^
net/core/dev.c:4363:1: warning: unused function 'sch_handle_egress'
[-Wunused-function]
sch_handle_egress(struct sk_buff *skb, int *ret, struct net_device *dev)
^
net/core/dev.c:5573:19: warning: unused function 'nf_ingress'
[-Wunused-function]
static inline int nf_ingress(struct sk_buff *skb, struct packet_type
**pt_prev,
^
5 warnings generated.
vim +2072 net/core/dev.c
2060
2061 void __netdev_dmabuf_binding_free(struct netdev_dmabuf_binding *binding)
2062 {
2063 size_t size, avail;
2064
2065 gen_pool_for_each_chunk(binding->chunk_pool,
2066 netdev_dmabuf_free_chunk_owner, NULL);
2067
2068 size = gen_pool_size(binding->chunk_pool);
2069 avail = gen_pool_avail(binding->chunk_pool);
2070
2071 if (!WARN(size != avail, "can't destroy genpool. size=%lu,
avail=%lu",
> 2072size, avail))
2073 gen_pool_destroy(binding->chunk_pool);
2074
2075 dma_buf_unmap_attachment(binding->attachment, binding->sgt,
2076 DMA_BIDIRECTIONAL);
2077 dma_buf_detach(binding->dmabuf, binding->attachment);
2078 dma_buf_put(binding->dmabuf);
2079 xa_destroy(&binding->bound_rxq_list);
2080 kfree(binding);
2081 }
2082
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next 3/3] selftests/net: fix GRO coalesce test and add ext
Hi Richard, kernel test robot noticed the following build warnings: [auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Richard-Gobert/net-gso-add-HBH-extension-header-offload-support/20231222-172059 base: net-next/main patch link: https://lore.kernel.org/r/641157c0-f224-4910-874d-7906a48d914b%40gmail.com patch subject: [PATCH net-next 3/3] selftests/net: fix GRO coalesce test and add ext compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231223/202312231344.swss5pik-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202312231344.swss5pik-...@intel.com/ All warnings (new ones prefixed by >>): gro.c: In function 'add_ipv6_exthdr': >> gro.c:600:13: warning: variable 'opt_len' set but not used >> [-Wunused-but-set-variable] 600 | int opt_len; | ^~~ -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[broonie-ci:kselftest-seccomp-benchmark-ktap] [kselftest/seccomp] bb94019905: kernel-selftests.seccomp.seccomp_benchmark.fail
Hello,
kernel test robot noticed "kernel-selftests.seccomp.seccomp_benchmark.fail" on:
commit: bb94019905757de0ddac22e897b7648b55aeef8e ("kselftest/seccomp: Report
each expectation we assert as a KTAP test")
https://git.kernel.org/cgit/linux/kernel/git/broonie/ci.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
| Closes:
https://lore.kernel.org/oe-lkp/202312271441.2e64d159-oliver.s...@intel.com
# timeout set to 120
# selftests: seccomp: seccomp_benchmark
# TAP version 13
# 1..7
# # Running on:
# # Linux lkp-csl-d01 6.7.0-rc3-3-gbb9401990575 #1 SMP PREEMPT_DYNAMIC Mon
Dec 25 09:40:50 CST 2023 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 37997130 syscalls...
# # 15.768643565 - 1.028667802 = 14739975763 (14.7s)
# # getpid native: 387 ns
# # 32.305042795 - 15.769439484 = 16535603311 (16.5s)
# # getpid RET_ALLOW 1 filter (bitmap): 435 ns
# # 48.595567892 - 32.307930690 = 16287637202 (16.3s)
# # getpid RET_ALLOW 2 filters (bitmap): 428 ns
# # 67.773953317 - 48.596835421 = 19177117896 (19.2s)
# # getpid RET_ALLOW 3 filters (full): 504 ns
# # 88.068486378 - 67.774726217 = 20293760161 (20.3s)
# # getpid RET_ALLOW 4 filters (full): 534 ns
# # Estimated total seccomp overhead for 1 bitmapped filter: 48 ns
# # Estimated total seccomp overhead for 2 bitmapped filters: 41 ns
# # Estimated total seccomp overhead for 3 full filters: 117 ns
# # Estimated total seccomp overhead for 4 full filters: 147 ns
# # Estimated seccomp entry overhead: 55 ns
# # Estimated seccomp per-filter overhead (last 2 diff): 30 ns
# # Estimated seccomp per-filter overhead (filters / 4): 23 ns
# # Expectations:
# # native ≤ 1 bitmap (387 ≤ 435): ✔️
# ok 1 native ≤ 1 bitmap
# # native ≤ 1 filter (387 ≤ 504): ✔️
# ok 2 native ≤ 1 filter
# # per-filter (last 2 diff) ≈ per-filter (filters / 4) (30 ≈ 23): ❌
# not ok 3 per-filter (last 2 diff) ≈ per-filter (filters / 4)
# # 1 bitmapped ≈ 2 bitmapped (48 ≈ 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/20231227/202312271441.2e64d159-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linux-next:master] BUILD REGRESSION d0b3c8aa5e37775cd7c3ac07b256218df0fd6678
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: d0b3c8aa5e37775cd7c3ac07b256218df0fd6678 Add linux-next specific
files for 20240104
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202401041942.qrb1amzm-...@intel.com
Error/Warning: (recently discovered and may have been fixed)
tools/testing/selftests/net/tcp_ao/bench-lookups.c:202: undefined reference to
`sqrt'
Unverified Error/Warning (likely false positive, please contact us if
interested):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:9280
amdgpu_dm_atomic_commit_tail() error: we previously assumed 'acrtc' could be
null (see line 9277)
drivers/media/i2c/st-mipid02.c:396:1-7: WARNING: do_div() does a 64-by-32
division, please consider using div64_s64 instead.
drivers/net/ethernet/broadcom/bnxt/bnxt.c:5333:6-25: WARNING:
atomic_dec_and_test variation before object free at line 5336.
drivers/net/ethernet/marvell/octeon_ep/octep_pfvf_mbox.c:32:16-17: WARNING
opportunity for min()
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:575:9-32: duplicated
argument to & or |
{standard input}:18305: Warning: overflow in branch to .L4391; converted into
longer instruction sequence
{standard input}:20816: Warning: overflow in branch to .L4982; converted into
longer instruction sequence
{standard input}:21171: Warning: overflow in branch to .L4853; converted into
longer instruction sequence
{standard input}:27179: Warning: overflow in branch to .L4887; converted into
longer instruction sequence
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
|-- alpha-allyesconfig
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs
| `--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs
|-- arc-allmodconfig
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs
| `--
drivers-gpu-drm-msm-disp-dpu1-dpu_encoder.c:warning:Excess-struct-member-debugfs_root-description-in-dpu_encoder_virt
|-- arc-allyesconfig
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs
| `--
drivers-gpu-drm-msm-disp-dpu1-dpu_encoder.c:warning:Excess-struct-member-debugfs_root-description-in-dpu_encoder_virt
|-- arc-randconfig-002-20240104
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs
| `--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs
|-- arc-randconfig-r133-20240104
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs
| |--
drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-me
[linux-next:master] BUILD REGRESSION 8d04a7e2ee3fd6aabb8096b00c64db0d735bc874
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 8d04a7e2ee3fd6aabb8096b00c64db0d735bc874 Add linux-next specific files for 20240112 Error/Warning: (recently discovered and may have been fixed) WARNING: modpost: vmlinux: section mismatch in reference: size_mul+0x40 (section: .text.unlikely) -> initcall_level_names (section: .init.data) Unverified Error/Warning (likely false positive, please contact us if interested): (.exception.text+0x25b): dangerous relocation: windowed longcall crosses 1GB boundary; return may fail: make_task_dead WARNING: modpost: vmlinux: section mismatch in reference: vmap_block_vaddr.part.0+0x28 (section: .text.unlikely) -> initcall_level_names (section: .init.data) Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs | `-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs |-- arc-allmodconfig | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs | `-- drivers-gpu-drm-msm-disp-dpu1-dpu_encoder.c:warning:Excess-struct-member-debugfs_root-description-in-dpu_encoder_virt |-- arc-allyesconfig | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs | `-- drivers-gpu-drm-msm-disp-dpu1-dpu_encoder.c:warning:Excess-struct-member-debugfs_root-description-in-dpu_encoder_virt |-- arc-randconfig-001-20240112 | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs | `-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs |-- arc-randconfig-r132-20240113 | |-- drivers-usb-gadget-function-f_ncm.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-unsigned-short-usertype-max_segment_size-got-restricted-__le16-usertype | |-- fs-bcachefs-btree_iter.c:sparse:sparse:incompatible-types-in-comparison-expression-(different-address-spaces): | `-- fs-bcachefs-btree_locking.c:sparse:sparse:incompatible-types-in-comparison-expression-(different-address-spaces): |-- arm-allmodconfig | |-- WARNING:modpost:vmlinux:section-mismatch-in-reference:vmap_init_free_space-(section:.text.unlikely)-vmlist-(section:.init.data) | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-dst_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-filled_descs_num-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-size-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-src_addr-not-described-in-xdma_fill_descs | |-- drivers-dma-xilinx-xdma.c:warning:Function-parameter-or-struct-member-sw_desc-not-described-in-xdma_fill_descs | `-- drivers-gpu-drm-msm-disp-dpu1-dpu_encoder.c:warning:Excess-struct-member-debugfs_root-description-in-dpu_encoder_virt |-- arm-allyesconfig | |-- WAR
Re: [PATCH v3] selftests/landlock:Fix two build issues
Hi Hu,
kernel test robot noticed the following build errors:
[auto build test ERROR on shuah-kselftest/next]
[also build test ERROR on shuah-kselftest/fixes linus/master v6.7 next-20240112]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Hu-Yadi/selftests-landlock-Fix-two-build-issues/20240112-151805
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:https://lore.kernel.org/r/20240112071245.669-1-hu.yadi%40h3c.com
patch subject: [PATCH v3] selftests/landlock:Fix two build issues
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240115/202401151147.t1s11ihj-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202401151147.t1s11ihj-...@intel.com/
All errors (new ones prefixed by >>):
>> net_test.c:25:14: error: static declaration of 'gettid' follows non-static
>> declaration
25 | static pid_t gettid(void)
| ^~
In file included from /usr/include/unistd.h:1218,
from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24,
from /usr/include/signal.h:328,
from /usr/include/x86_64-linux-gnu/sys/wait.h:36,
from common.h:16,
from net_test.c:22:
/usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous
declaration of 'gettid' with type '__pid_t(void)' {aka 'int(void)'}
34 | extern __pid_t gettid (void) __THROW;
|^~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] riscv: mm: Use hint address in mmap if available
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on 556e2d17cae620d549c5474b1ece053430cd50bc]
url:
https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/riscv-mm-Use-hint-address-in-mmap-if-available/20240130-084208
base: 556e2d17cae620d549c5474b1ece053430cd50bc
patch link:
https://lore.kernel.org/r/20240129-use_mmap_hint_address-v1-1-4c74da813ba1%40rivosinc.com
patch subject: [PATCH 1/3] riscv: mm: Use hint address in mmap if available
config: riscv-defconfig
(https://download.01.org/0day-ci/archive/20240131/202401310404.enjvhoc9-...@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240131/202401310404.enjvhoc9-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202401310404.enjvhoc9-...@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/riscv/include/asm/irqflags.h:10,
from include/linux/irqflags.h:18,
from arch/riscv/include/asm/bitops.h:14,
from include/linux/bitops.h:68,
from include/linux/kernel.h:23,
from mm/mmap.c:12:
mm/mmap.c: In function 'generic_get_unmapped_area':
>> arch/riscv/include/asm/processor.h:28:9: error: expected expression before
>> 'else'
28 | else\
| ^~~~
mm/mmap.c:1703:40: note: in expansion of macro 'arch_get_mmap_end'
1703 | const unsigned long mmap_end = arch_get_mmap_end(addr, len,
flags);
|^
mm/mmap.c: In function 'generic_get_unmapped_area_topdown':
>> arch/riscv/include/asm/processor.h:28:9: error: expected expression before
>> 'else'
28 | else\
| ^~~~
mm/mmap.c:1751:40: note: in expansion of macro 'arch_get_mmap_end'
1751 | const unsigned long mmap_end = arch_get_mmap_end(addr, len,
flags);
|^
--
In file included from arch/riscv/include/asm/irqflags.h:10,
from include/linux/irqflags.h:18,
from arch/riscv/include/asm/bitops.h:14,
from include/linux/bitops.h:68,
from include/linux/thread_info.h:27,
from fs/hugetlbfs/inode.c:12:
fs/hugetlbfs/inode.c: In function 'hugetlb_get_unmapped_area_bottomup':
>> arch/riscv/include/asm/processor.h:28:9: error: expected expression before
>> 'else'
28 | else\
| ^~~~
fs/hugetlbfs/inode.c:173:27: note: in expansion of macro 'arch_get_mmap_end'
173 | info.high_limit = arch_get_mmap_end(addr, len, flags);
| ^
fs/hugetlbfs/inode.c: In function 'hugetlb_get_unmapped_area_topdown':
>> arch/riscv/include/asm/processor.h:28:9: error: expected expression before
>> 'else'
28 | else\
| ^~~~
fs/hugetlbfs/inode.c:204:35: note: in expansion of macro 'arch_get_mmap_end'
204 | info.high_limit = arch_get_mmap_end(addr, len,
flags);
| ^
fs/hugetlbfs/inode.c: In function 'generic_hugetlb_get_unmapped_area':
>> arch/riscv/include/asm/processor.h:28:9: error: expected expression before
>> 'else'
28 | else\
| ^~~~
fs/hugetlbfs/inode.c:219:40: note: in expansion of macro 'arch_get_mmap_end'
219 | const unsigned long mmap_end = arch_get_mmap_end(addr, len,
flags);
|^
vim +/else +28 arch/riscv/include/asm/processor.h
add2cc6b6515f7 Charlie Jenkins 2023-08-09 20
add2cc6b6515f7 Charlie Jenkins 2023-08-09 21 #define arch_get_mmap_end(addr,
len, flags) \
add2cc6b6515f7 Charlie Jenkins 2023-08-09 22 ({
\
add2cc6b6515f7 Charlie Jenkins 2023-08-09 23 unsigned long mmap_end;
\
add2cc6b6515f7 Charlie Jenkins 2023-08-09 24 typeof(addr) _addr = (addr);
\
c5712238cfe3f5 Charlie Jenkins 2024-01-29 25 if ((_addr) == 0 ||
Re: [PATCH 1/3] riscv: mm: Use hint address in mmap if available
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on 556e2d17cae620d549c5474b1ece053430cd50bc]
url:
https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/riscv-mm-Use-hint-address-in-mmap-if-available/20240130-084208
base: 556e2d17cae620d549c5474b1ece053430cd50bc
patch link:
https://lore.kernel.org/r/20240129-use_mmap_hint_address-v1-1-4c74da813ba1%40rivosinc.com
patch subject: [PATCH 1/3] riscv: mm: Use hint address in mmap if available
config: riscv-allnoconfig
(https://download.01.org/0day-ci/archive/20240131/202401310513.lub8ilwm-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
fdac7d0b6f74f919d319b31a0680c77f66732586)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240131/202401310513.lub8ilwm-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202401310513.lub8ilwm-...@intel.com/
All errors (new ones prefixed by >>):
>> mm/mmap.c:1703:33: error: expected expression
1703 | const unsigned long mmap_end = arch_get_mmap_end(addr, len,
flags);
|^
arch/riscv/include/asm/processor.h:28:2: note: expanded from macro
'arch_get_mmap_end'
28 | else\
| ^
mm/mmap.c:1751:33: error: expected expression
1751 | const unsigned long mmap_end = arch_get_mmap_end(addr, len,
flags);
|^
arch/riscv/include/asm/processor.h:28:2: note: expanded from macro
'arch_get_mmap_end'
28 | else\
| ^
2 errors generated.
vim +1703 mm/mmap.c
f6795053dac8d4d Steve Capper 2018-12-06 1683
^1da177e4c3f415 Linus Torvalds 2005-04-16 1684 /* Get an address
range which is currently unmapped.
^1da177e4c3f415 Linus Torvalds 2005-04-16 1685 * For shmat() with
addr=0.
^1da177e4c3f415 Linus Torvalds 2005-04-16 1686 *
^1da177e4c3f415 Linus Torvalds 2005-04-16 1687 * Ugly calling
convention alert:
^1da177e4c3f415 Linus Torvalds 2005-04-16 1688 * Return value with
the low bits set means error value,
^1da177e4c3f415 Linus Torvalds 2005-04-16 1689 * ie
^1da177e4c3f415 Linus Torvalds 2005-04-16 1690 * if (ret &
~PAGE_MASK)
^1da177e4c3f415 Linus Torvalds 2005-04-16 1691 * error =
ret;
^1da177e4c3f415 Linus Torvalds 2005-04-16 1692 *
^1da177e4c3f415 Linus Torvalds 2005-04-16 1693 * This function
"knows" that -ENOMEM has the bits set.
^1da177e4c3f415 Linus Torvalds 2005-04-16 1694 */
^1da177e4c3f415 Linus Torvalds 2005-04-16 1695 unsigned long
4b439e25e29ec33 Christophe Leroy 2022-04-09 1696
generic_get_unmapped_area(struct file *filp, unsigned long addr,
4b439e25e29ec33 Christophe Leroy 2022-04-09 1697
unsigned long len, unsigned long pgoff,
4b439e25e29ec33 Christophe Leroy 2022-04-09 1698
unsigned long flags)
^1da177e4c3f415 Linus Torvalds 2005-04-16 1699 {
^1da177e4c3f415 Linus Torvalds 2005-04-16 1700 struct
mm_struct *mm = current->mm;
1be7107fbe18eed Hugh Dickins 2017-06-19 1701 struct
vm_area_struct *vma, *prev;
db4fbfb9523c935 Michel Lespinasse 2012-12-11 1702 struct
vm_unmapped_area_info info;
2cb4de085f383cb Christophe Leroy 2022-04-09 @1703 const unsigned
long mmap_end = arch_get_mmap_end(addr, len, flags);
^1da177e4c3f415 Linus Torvalds 2005-04-16 1704
f6795053dac8d4d Steve Capper 2018-12-06 1705 if (len >
mmap_end - mmap_min_addr)
^1da177e4c3f415 Linus Torvalds 2005-04-16 1706 return
-ENOMEM;
^1da177e4c3f415 Linus Torvalds 2005-04-16 1707
06abdfb47ee745a Benjamin Herrenschmidt 2007-05-06 1708 if (flags &
MAP_FIXED)
06abdfb47ee745a Benjamin Herrenschmidt 2007-05-06 1709 return
addr;
06abdfb47ee745a Benjamin Herrenschmidt 2007-05-06 1710
^1da177e4c3f415 Linus Torvalds 2005-04-16 1711 if (addr) {
^1da177e4c3f415 Linus Torvalds 2005-04-16 1712 addr =
PAGE_ALIGN(addr);
1be7107fbe18eed Hugh Dickins 2017-06-19 1713 vma =
find_vma_prev(mm, addr, &prev);
f6795053dac8d4d Steve Capper 2018-12-06 1714 if
(mmap_end - len >= addr && addr >= mmap_min_addr &&
1be7107fbe18eed Hugh Dickins 2017-06-19 1715
(!vma || addr + le
Re: [PATCH bpf-next v4 3/3] bpf: treewide: Annotate BPF kfuncs in BTF
Hello,
kernel test robot noticed
"WARNING:at_kernel/bpf/btf.c:#register_btf_kfunc_id_set" on:
commit: 918c4c7dda155568c619b4082fa83ca90ab578a6 ("[PATCH bpf-next v4 3/3] bpf:
treewide: Annotate BPF kfuncs in BTF")
url:
https://github.com/intel-lab-lkp/linux/commits/Daniel-Xu/bpf-btf-Support-flags-for-BTF_SET8-sets/20240129-092732
base: https://git.kernel.org/cgit/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/all/e55150ceecbf0a5d961e608941165c0bee7bc943.1706491398.git@dxuuu.xyz/
patch subject: [PATCH bpf-next v4 3/3] bpf: treewide: Annotate BPF kfuncs in BTF
in testcase: boot
compiler: clang-17
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-+++
| | 05221438c4
| 918c4c7dda |
+-+++
| WARNING:at_kernel/bpf/btf.c:#register_btf_kfunc_id_set | 0
| 7 |
| EIP:register_btf_kfunc_id_set | 0
| 7 |
| calltrace:do_softirq_own_stack | 0
| 7 |
+-+++
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
| Closes: https://lore.kernel.org/oe-lkp/202402041610.775e7f75-...@intel.com
[ 49.044594][T1] [ cut here ]
[ 49.045857][ T1] WARNING: CPU: 1 PID: 1 at kernel/bpf/btf.c:8048
register_btf_kfunc_id_set (??:?)
[ 49.048024][T1] Modules linked in:
[ 49.048925][T1] CPU: 1 PID: 1 Comm: swapper/0 Tainted: GW
6.8.0-rc1-00457-g918c4c7dda15 #6
[ 49.051230][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 49.053616][ T1] EIP: register_btf_kfunc_id_set (??:?)
[ 49.054969][ T1] Code: 04 01 75 0b b8 ea ff ff ff 83 3a 00 74 1c c3 b9 0d 00
00 00 83 f8 20 77 07 8b 0c 85 28 a2 71 d7 55 89 e5 e8 13 00 00 00 5d c3 <0f> 0b
c3 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 53 57
All code
0: 04 01 add$0x1,%al
2: 75 0b jne0xf
4: b8 ea ff ff ff mov$0xffea,%eax
9: 83 3a 00cmpl $0x0,(%rdx)
c: 74 1c je 0x2a
e: c3 retq
f: b9 0d 00 00 00 mov$0xd,%ecx
14: 83 f8 20cmp$0x20,%eax
17: 77 07 ja 0x20
19: 8b 0c 85 28 a2 71 d7mov-0x288e5dd8(,%rax,4),%ecx
20: 55 push %rbp
21: 89 e5 mov%esp,%ebp
23: e8 13 00 00 00 callq 0x3b
28: 5d pop%rbp
29: c3 retq
2a:* 0f 0b ud2 <-- trapping instruction
2c: c3 retq
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 90 nop
31: 90 nop
32: 90 nop
33: 90 nop
34: 90 nop
35: 90 nop
36: 90 nop
37: 90 nop
38: 90 nop
39: 90 nop
3a: 90 nop
3b: 55 push %rbp
3c: 89 e5 mov%esp,%ebp
3e: 53 push %rbx
3f: 57 push %rdi
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: c3 retq
3: 90 nop
4: 90 nop
5: 90 nop
6: 90 nop
7: 90 nop
8: 90 nop
9: 90 nop
a: 90 nop
b: 90 nop
c: 90 nop
d: 90 nop
e: 90 nop
f: 90 nop
10: 90 nop
11: 55 push %rbp
12: 89 e5 mov%esp,%ebp
14: 53 push %rbx
15: 57 push %rdi
[ 49.059550][T1] EAX: ffea EBX: ECX: d9356fb0 EDX: d7c2b154
[ 49.061229][T1] ESI: EDI: 019a EBP: c028dc48 ESP: c028dc38
[ 49.062886][T
[broonie-misc:kselftest-seccomp-benchmark-ktap] [kselftest/seccomp] 626fa92237: kernel-selftests.seccomp.seccomp_benchmark.fail
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
| Closes:
https://lore.kernel.org/oe-lkp/202402061002.3a8722fd-oliver.s...@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-3-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.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] pstore: add multi-backend support
Hi Yuanhe, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/pstore] [also build test ERROR on kees/for-next/kspp shuah-kselftest/next shuah-kselftest/fixes linus/master v6.8-rc3 next-20240205] [cannot apply to aegl/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Yuanhe-Shu/pstore-add-multi-backend-support/20240205-203438 base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore patch link: https://lore.kernel.org/r/20240205122852.7069-2-xiangzao%40linux.alibaba.com patch subject: [PATCH 1/3] pstore: add multi-backend support config: csky-randconfig-r071-20240206 (https://download.01.org/0day-ci/archive/20240206/202402061551.eklbf7yd-...@intel.com/config) compiler: csky-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240206/202402061551.eklbf7yd-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202402061551.eklbf7yd-...@intel.com/ All error/warnings (new ones prefixed by >>): >> fs/pstore/ftrace.c:30:47: warning: 'struct ftrace_info' declared inside >> parameter list will not be visible outside of this definition or declaration 30 |struct ftrace_info *psinfo) | ^~~ fs/pstore/ftrace.c: In function 'pstore_do_ftrace': >> fs/pstore/ftrace.c:39:24: error: initialization of 'struct pstore_info *' >> from incompatible pointer type 'struct ftrace_info *' >> [-Werror=incompatible-pointer-types] 39 | .psi = psinfo, |^~ fs/pstore/ftrace.c:39:24: note: (near initialization for 'record.psi') >> fs/pstore/ftrace.c:55:15: error: invalid use of undefined type 'struct >> ftrace_info' 55 | psinfo->write(&record); | ^~ fs/pstore/ftrace.c: In function 'pstore_ftrace_call': >> fs/pstore/ftrace.c:71:61: error: passing argument 4 of 'pstore_do_ftrace' >> from incompatible pointer type [-Werror=incompatible-pointer-types] 71 | pstore_do_ftrace(ip, parent_ip, op, regs, entry->psi); | ^~~~ | | | struct pt_regs * fs/pstore/ftrace.c:29:60: note: expected 'struct ftrace_regs *' but argument is of type 'struct pt_regs *' 29 |struct ftrace_regs *fregs, |^ fs/pstore/ftrace.c:71:72: error: passing argument 5 of 'pstore_do_ftrace' from incompatible pointer type [-Werror=incompatible-pointer-types] 71 | pstore_do_ftrace(ip, parent_ip, op, regs, entry->psi); | ~^ | | | struct pstore_info * fs/pstore/ftrace.c:30:60: note: expected 'struct ftrace_info *' but argument is of type 'struct pstore_info *' 30 |struct ftrace_info *psinfo) |^~ fs/pstore/ftrace.c: At top level: >> fs/pstore/ftrace.c:76:19: error: initialization of 'void (*)(long unsigned >> int, long unsigned int, struct ftrace_ops *, struct ftrace_regs *)' from >> incompatible pointer type 'void (*)(long unsigned int, long unsigned int, >> struct ftrace_ops *, struct pt_regs *)' [-Werror=incompatible-pointer-types] 76 | .func = pstore_ftrace_call, | ^~ fs/pstore/ftrace.c:76:19: note: (near initialization for 'pstore_ftrace_ops.func') In file included from include/linux/dcache.h:8, from include/linux/fs.h:8, from include/linux/huge_mm.h:8, from include/linux/mm.h:1095, from include/linux/kallsyms.h:13, from include/linux/ftrace.h:13,
Re: [PATCH 1/3] pstore: add multi-backend support
Hi Yuanhe, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/pstore] [also build test ERROR on kees/for-next/kspp shuah-kselftest/next shuah-kselftest/fixes linus/master v6.8-rc3 next-20240206] [cannot apply to aegl/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Yuanhe-Shu/pstore-add-multi-backend-support/20240205-203438 base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore patch link: https://lore.kernel.org/r/20240205122852.7069-2-xiangzao%40linux.alibaba.com patch subject: [PATCH 1/3] pstore: add multi-backend support config: i386-buildonly-randconfig-004-20240206 (https://download.01.org/0day-ci/archive/20240206/202402062036.5fpfksgi-...@intel.com/config) compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240206/202402062036.5fpfksgi-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202402062036.5fpfksgi-...@intel.com/ All errors (new ones prefixed by >>): fs/pstore/ftrace.c:30:19: warning: declaration of 'struct ftrace_info' will not be visible outside of this function [-Wvisibility] 30 |struct ftrace_info *psinfo) | ^ >> fs/pstore/ftrace.c:39:10: error: incompatible pointer types initializing >> 'struct pstore_info *' with an expression of type 'struct ftrace_info *' >> [-Werror,-Wincompatible-pointer-types] 39 | .psi = psinfo, |^~ >> fs/pstore/ftrace.c:55:8: error: incomplete definition of type 'struct >> ftrace_info' 55 | psinfo->write(&record); | ~~^ fs/pstore/ftrace.c:30:19: note: forward declaration of 'struct ftrace_info' 30 |struct ftrace_info *psinfo) | ^ >> fs/pstore/ftrace.c:71:40: error: incompatible pointer types passing 'struct >> pt_regs *' to parameter of type 'struct ftrace_regs *' >> [-Werror,-Wincompatible-pointer-types] 71 | pstore_do_ftrace(ip, parent_ip, op, regs, entry->psi); | ^~~~ fs/pstore/ftrace.c:29:32: note: passing argument to parameter 'fregs' here 29 |struct ftrace_regs *fregs, |^ >> fs/pstore/ftrace.c:71:46: error: incompatible pointer types passing 'struct >> pstore_info *' to parameter of type 'struct ftrace_info *' >> [-Werror,-Wincompatible-pointer-types] 71 | pstore_do_ftrace(ip, parent_ip, op, regs, entry->psi); | ^~ fs/pstore/ftrace.c:30:32: note: passing argument to parameter 'psinfo' here 30 |struct ftrace_info *psinfo) |^ >> fs/pstore/ftrace.c:76:10: error: incompatible function pointer types >> initializing 'ftrace_func_t' (aka 'void (*)(unsigned long, unsigned long, >> struct ftrace_ops *, struct ftrace_regs *)') with an expression of type >> 'void (unsigned long, unsigned long, struct ftrace_ops *, struct pt_regs *)' >> [-Wincompatible-function-pointer-types] 76 | .func = pstore_ftrace_call, | ^~ >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' 150 | list_for_each_entry_rcu(entry, &psback->list_entry, list) | ^ >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' >> fs/pstore/ftrace.c:150:26: error: use of undeclared identifier 'entry' >>
[linux-next:master] BUILD REGRESSION ac139fc7db67968e5061715508b5fc4aa7c40c56
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: ac139fc7db67968e5061715508b5fc4aa7c40c56 Add linux-next specific files for 20240206 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202402061900.rtuydlo6-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402062106.cfarbjsv-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402062134.a6cqat3s-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402062139.mkzns4qf-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402062151.kq60k2lk-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402062210.3yybvgf1-...@intel.com Error/Warning: (recently discovered and may have been fixed) arch/sh/boot/compressed/../../../../lib/xz/xz_dec_lzma2.c:648:(.text+0xaf0): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/sh/boot/compressed/../../../../lib/zlib_inflate/inffast.c:132:(.text+0x738): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/sh/boot/compressed/../../../../lib/zlib_inflate/inflate.c:57:(.text+0xbd0): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/sh/boot/compressed/../../../../lib/zlib_inflate/inftrees.c:270:(.text+0x3dc): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/xtensa/boot/lib/inflate.c:91:(.text+0x1a4): undefined reference to `__ubsan_handle_out_of_bounds' drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c:1955: warning: Function parameter or struct member 'gsp' not described in 'nvkm_gsp_radix3_sg' fs/ceph/locks.c:379:27: warning: unused variable 'lock' [-Wunused-variable] make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop. powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data202' from `fs/overlayfs/copy_up.o' being placed in section `.bss..Lubsan_data202' powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data219' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data219' powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data327' from `kernel/sched/core.o' being placed in section `.bss..Lubsan_data327' sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/zlib_inflate/inffast.c:305:(.text+0xac4): undefined reference to `__ubsan_handle_shift_out_of_bounds' sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/zlib_inflate/inftrees.c:315:(.text+0x60c): undefined reference to `__ubsan_handle_shift_out_of_bounds' sh4-linux-ld: arch/sh/boot/compressed/misc.o:(.debug_addr+0x388): undefined reference to `__ubsan_handle_shift_out_of_bounds' sh4-linux-ld: misc.c:(.text+0x23d4): undefined reference to `__ubsan_handle_shift_out_of_bounds' xtensa-linux-ld: arch/xtensa/boot/lib/inflate.c:487:(.text+0x546): undefined reference to `__ubsan_handle_out_of_bounds' Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- arc-randconfig-r113-20240206 | `-- drivers-gpu-drm-bridge-imx-imx8mp-hdmi-pvi.c:sparse:sparse:Using-plain-integer-as-NULL-pointer |-- arm-randconfig-r071-20240206 | `-- fs-ceph-locks.c:warning:unused-variable-lock |-- i386-buildonly-randconfig-003-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-014-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-016-20240206 | `-- include-kunit-test.h:warning:s-directive-argument-is-null |-- i386-randconfig-052-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- mips-allyesconfig | |-- (.ref.text):relocation-truncated-to-fit:R_MIPS_26-against-start_secondary | `-- (.text):relocation-truncated-to-fit:R_MIPS_26-against-kernel_entry |-- nios2-randconfig-001-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- parisc-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- parisc-randconfig-001-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- powerpc-randconfig-r022-20230201 | |-- powerpc-linux-ld:warning:orphan-section-bss..Lubsan_data202-from-fs-overlayfs-copy_up.o-being-placed-in-section-.bss..Lubsan_data202 | |-- powerpc-linux-ld:warning:orphan-section-bss..Lubsan_data219-from-kernel-ptrace.o-being-placed-in-section-.bss..Lubsan_data219 | `-- powerpc-linux-ld:warning:orphan-section-bss..Lubsan_data327-from-kernel-sched-core.o-being-placed-in-section-.bss..Lubsan_data327 |-- powerpc64-randconfig-003-20240206 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- sh-randconfig-r003-20220501 | |-- arch-sh-boot-compressed-..-..-..-..-lib-zlib_inflate-inffast.c:(.text):undefined-reference-to-__ubsan_handle_shift_out_of_bounds | |-- arch-sh-boot-compressed-..-..-..-..-lib-zlib_inflate-inflate.c:(.text):undefined-reference-to-__ubsan_handle_shift_out_of_bounds | |-- arch-sh-boot-compressed-..-..-..-..-lib-zlib_inflate-inftrees.c:(.text):undefined-reference-to-__ubsan_handle_shift_out_of_bounds | |-- sh4-linux-ld:arch-sh-boot-comp
[linux-next:master] BUILD REGRESSION 445a555e0623387fa9b94e68e61681717e70200a
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 445a555e0623387fa9b94e68e61681717e70200a Add linux-next specific files for 20240209 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202402091752.dgmpja49-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402091848.rfysykyw-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402092153.btekesmi-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402100625.m0rkjhmh-...@intel.com Error/Warning: (recently discovered and may have been fixed) arch/sh/boot/compressed/../../../../lib/zlib_inflate/inflate.c:503:(.text+0x11d0): undefined reference to `__ubsan_handle_out_of_bounds' arch/sh/boot/compressed/../../../../lib/zlib_inflate/inftrees.c:229:(.text+0x490): undefined reference to `__ubsan_handle_out_of_bounds' arch/xtensa/boot/lib/inffast.c:113:(.text+0x9b): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/xtensa/boot/lib/inftrees.c:219:(.text+0x3e7): undefined reference to `__ubsan_handle_shift_out_of_bounds' arch/xtensa/boot/lib/inftrees.c:94:(.text+0xcf): undefined reference to `__ubsan_handle_out_of_bounds' kernel/locking/irqflag-debug.c:8:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes] kernel/locking/lockdep.c:883:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes] kernel/rcu/update.c:319:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes] kernel/sched/idle.c:53:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes] kernel/time/timekeeping.c:1045:1: warning: 'no_sanitize' attribute directive ignored [-Wattributes] kismet: WARNING: unmet direct dependencies detected for LEDS_EXPRESSWIRE when selected by BACKLIGHT_KTD2801 kismet: WARNING: unmet direct dependencies detected for LEDS_EXPRESSWIRE when selected by LEDS_KTD2692 make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop. s390-linux-ld: iptable_nat.c:(.text+0x14c): undefined reference to `ipt_register_table' s390-linux-ld: iptable_nat.c:(.text+0x330): undefined reference to `ipt_unregister_table_exit' s390-linux-ld: net/ipv4/netfilter/iptable_nat.o:(.data.rel.ro+0x0): undefined reference to `ipt_do_table' sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/zlib_inflate/inflate.c:547:(.text+0x1388): undefined reference to `__ubsan_handle_out_of_bounds' sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/zlib_inflate/inftrees.c:315:(.text+0x69c): undefined reference to `__ubsan_handle_out_of_bounds' xtensa-linux-ld: arch/xtensa/boot/lib/inffast.o:(.text+0x24): undefined reference to `__ubsan_handle_shift_out_of_bounds' xtensa-linux-ld: arch/xtensa/boot/lib/inftrees.o:(.text+0x84): undefined reference to `__ubsan_handle_shift_out_of_bounds' Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allnoconfig | |-- kismet:WARNING:unmet-direct-dependencies-detected-for-LEDS_EXPRESSWIRE-when-selected-by-BACKLIGHT_KTD2801 | `-- kismet:WARNING:unmet-direct-dependencies-detected-for-LEDS_EXPRESSWIRE-when-selected-by-LEDS_KTD2692 |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-randconfig-001-20240209 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arc-randconfig-002-20240209 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-002-20240209 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-003-20240209 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm-randconfig-r111-20240209 | `-- drivers-video-backlight-ktd2801-backlight.c:sparse:sparse:symbol-ktd2801_timing-was-not-declared.-Should-it-be-static |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member
[linux-next:master] BUILD REGRESSION ae00c445390b349e070a64dc62f08aa878db7248
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: ae00c445390b349e070a64dc62f08aa878db7248 Add linux-next specific files for 20240212 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202402122047.ydhrzmm4-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402130633.bfncwveh-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402131351.a0fzogeg-...@intel.com Error/Warning: (recently discovered and may have been fixed) drivers/md/dm.c:2131:(.text+0x9f34): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `set_dax_nocache' drivers/md/dm.c:2131:(.text+0x9f34): undefined reference to `set_dax_nocache' drivers/md/dm.c:2132:(.text+0x9f3c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `set_dax_nomc' misc.c:(.text+0x14f0): undefined reference to `__ubsan_handle_load_invalid_value' or1k-linux-ld: drivers/md/dm.c:2132:(.text+0x9f3c): undefined reference to `set_dax_nomc' sh4-linux-ld: misc.c:(.text+0x1698): undefined reference to `__ubsan_handle_load_invalid_value' Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-randconfig-002-20240212 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-001-20240212 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-001-20240212 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- csky-randconfig-002-20240212 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-r061-20240212 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-buildonly-randconfig-002-20240212 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-013-20240212 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-015-20240212 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- loongarch-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- loongarch-randconfig-002-20240212 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- microblaze-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- microblaze-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- mips-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- nios2-randconfig-001-20240212 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- openrisc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg
[linux-next:master] BUILD REGRESSION d37e1e4c52bc60578969f391fb81f947c3e83118
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: d37e1e4c52bc60578969f391fb81f947c3e83118 Add linux-next specific files for 20240216 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202402161359.furktcoz-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402161410.ig9i4odj-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402162252.fpea3zuy-...@intel.com Error/Warning: (recently discovered and may have been fixed) aarch64-linux-ld: ktd2801-backlight.c:(.text+0x118): undefined reference to `expresswire_power_off' aarch64-linux-ld: ktd2801-backlight.c:(.text+0x16c): undefined reference to `expresswire_enable' drivers/gpu/drm/tests/drm_buddy_test.c:(.text.drm_test_buddy_alloc_contiguous+0xb0): undefined reference to `__umoddi3' drivers/gpu/drm/tests/drm_buddy_test.c:48:(.text+0xfc): undefined reference to `__umoddi3' ktd2801-backlight.c:(.text+0x118): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `expresswire_power_off' ktd2801-backlight.c:(.text+0x16c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `expresswire_enable' ktd2801-backlight.c:(.text+0xe4): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `expresswire_write_u8' ktd2801-backlight.c:(.text+0xe4): undefined reference to `expresswire_write_u8' xtensa-linux-ld: arch/xtensa/boot/lib/inftrees.c:220:(.text+0x4d3): undefined reference to `__ubsan_handle_shift_out_of_bounds' xtensa-linux-ld: arch/xtensa/boot/lib/inftrees.c:96:(.text+0x152): undefined reference to `__ubsan_handle_out_of_bounds' Unverified Error/Warning (likely false positive, please contact us if interested): fs/btrfs/space-info.c:2012:13: warning: 'ret' may be used uninitialized [-Wmaybe-uninitialized] include/linux/netfilter/x_tables.h:372: undefined reference to `xt_recseq' include/linux/seqlock.h:72: undefined reference to `xt_recseq' ld: include/linux/netfilter/x_tables.h:379: undefined reference to `xt_recseq' ld: include/linux/seqlock.h:73: undefined reference to `xt_recseq' ld: net/ipv4/netfilter/arp_tables.c:1014: undefined reference to `xt_find_table_lock' ld: net/ipv4/netfilter/arp_tables.c:1469: undefined reference to `xt_find_revision' ld: net/ipv4/netfilter/arp_tables.c:1497: undefined reference to `xt_free_table_info' ld: net/ipv4/netfilter/arp_tables.c:1526: undefined reference to `xt_register_table' ld: net/ipv4/netfilter/arp_tables.c:1648: undefined reference to `xt_unregister_targets' ld: net/ipv4/netfilter/arp_tables.c:417: undefined reference to `xt_request_find_target' ld: net/ipv4/netfilter/arp_tables.c:432: undefined reference to `xt_percpu_counter_free' ld: net/ipv4/netfilter/arp_tables.c:900: undefined reference to `xt_request_find_table_lock' ld: net/ipv4/netfilter/arp_tables.c:912: undefined reference to `xt_replace_table' ld: net/ipv4/netfilter/arp_tables.c:944: undefined reference to `xt_table_unlock' ld: net/ipv4/netfilter/arptable_filter.c:67: undefined reference to `xt_hook_ops_alloc' ld: net/ipv4/netfilter/arptable_filter.c:75: undefined reference to `xt_unregister_template' net/ipv4/netfilter/arp_tables.c:1010: undefined reference to `xt_copy_counters' net/ipv4/netfilter/arp_tables.c:1040: undefined reference to `xt_table_unlock' net/ipv4/netfilter/arp_tables.c:1469: undefined reference to `xt_find_revision' net/ipv4/netfilter/arp_tables.c:1489: undefined reference to `xt_unregister_table' net/ipv4/netfilter/arp_tables.c:1513: undefined reference to `xt_alloc_table_info' net/ipv4/netfilter/arp_tables.c:1575: undefined reference to `xt_find_table' net/ipv4/netfilter/arp_tables.c:1614: undefined reference to `xt_proto_init' net/ipv4/netfilter/arp_tables.c:1619: undefined reference to `xt_proto_fini' net/ipv4/netfilter/arp_tables.c:1636: undefined reference to `xt_register_targets' net/ipv4/netfilter/arp_tables.c:1658: undefined reference to `xt_unregister_targets' net/ipv4/netfilter/arp_tables.c:369: undefined reference to `xt_find_jump_offset' net/ipv4/netfilter/arp_tables.c:401: undefined reference to `xt_check_target' net/ipv4/netfilter/arp_tables.c:413: undefined reference to `xt_percpu_counter_alloc' net/ipv4/netfilter/arp_tables.c:475: undefined reference to `xt_check_entry_offsets' net/ipv4/netfilter/arp_tables.c:513: undefined reference to `xt_percpu_counter_free' net/ipv4/netfilter/arp_tables.c:539: undefined reference to `xt_alloc_entry_offsets' net/ipv4/netfilter/arp_tables.c:565: undefined reference to `xt_check_table_hooks' net/ipv4/netfilter/arp_tables.c:611: undefined reference to `xt_recseq' net/ipv4/netfilter/arp_tables.c:706: undefined reference to `xt_target_to_user' net/ipv4/netfilter/arp_tables.c:808: undefined reference to `xt_request_find_table_lock' net/ipv4/netfilter/arp_tables.c:862: undefined reference to `xt_find_table_lock' net/ipv4/netfilter/arp_tables.c:894: undefined reference to `xt_counters_alloc' net/ipv4/netfilter/arptable_filter.c:61: un
Re: [PATCH net-next 1/4] selftests: kselftest_harness: pass step via shared memory
Hi Jakub, kernel test robot noticed the following build errors: [auto build test ERROR on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Jakub-Kicinski/selftests-kselftest_harness-pass-step-via-shared-memory/20240213-234644 base: net-next/main patch link: https://lore.kernel.org/r/20240213154416.422739-2-kuba%40kernel.org patch subject: [PATCH net-next 1/4] selftests: kselftest_harness: pass step via shared memory compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240219/202402191034.76fueppp-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202402191034.76fueppp-...@intel.com/ All errors (new ones prefixed by >>): In file included from fs_test.c:26: fs_test.c: In function 'layout1_no_restriction': >> common.h:52:40: error: 'struct __test_metadata' has no member named 'step' 52 | _exit(_metadata->step); \ |^~ fs_test.c:403:1: note: in expansion of macro 'TEST_F_FORK' 403 | TEST_F_FORK(layout1, no_restriction) | ^~~ common.h:58:34: error: 'struct __test_metadata' has no member named 'step' 58 | _metadata->step = 1; \ | ^~ fs_test.c:403:1: note: in expansion of macro 'TEST_F_FORK' 403 | TEST_F_FORK(layout1, no_restriction) | ^~~ common.h:71:34: error: 'struct __test_metadata' has no member named 'step' 71 | _metadata->step = WEXITSTATUS(status); \ | ^~ fs_test.c:403:1: note: in expansion of macro 'TEST_F_FORK' 403 | TEST_F_FORK(layout1, no_restriction) | ^~~ fs_test.c: In function 'layout1_inval': >> common.h:52:40: error: 'struct __test_metadata' has no member named 'step' 52 | _exit(_metadata->step); \ |^~ fs_test.c:426:1: note: in expansion of macro 'TEST_F_FORK' 426 | TEST_F_FORK(layout1, inval) | ^~~ common.h:58:34: error: 'struct __test_metadata' has no member named 'step' 58 | _metadata->step = 1; \ | ^~ fs_test.c:426:1: note: in expansion of macro 'TEST_F_FORK' 426 | TEST_F_FORK(layout1, inval) | ^~~ common.h:71:34: error: 'struct __test_metadata' has no member named 'step' 71 | _metadata->step = WEXITSTATUS(status); \ | ^~ fs_test.c:426:1: note: in expansion of macro 'TEST_F_FORK' 426 | TEST_F_FORK(layout1, inval) | ^~~ fs_test.c: In function 'layout1_file_and_dir_access_rights': >> common.h:52:40: error: 'struct __test_metadata' has no member named 'step' 52 | _exit(_metadata->step); \ |^~ fs_test.c:548:1: note: in expansion of macro 'TEST_F_FORK' 548 | TEST_F_FORK(layout1, file_and_dir_access_rights) | ^~~ common.h:58:34: error: 'struct __test_metadata' has no member named 'step' 58 | _metadata->step = 1; \ | ^~ fs_test.c:548:1: note: in expansion of macro 'TEST_F_FORK' 548 | TEST_F_FORK(layout1, file_and_dir_access_rights) | ^~~ common.h:71:34: error: 'struct __test_metadata' has no member named 'step' 71 | _metadata->step = WEXITSTATUS(status); \ | ^~ fs_test.c:548:1: note: in expansion of macro 'TEST_F_FORK' 548 | TEST_F_FORK(layout1, file_and_dir_access_rights) | ^~~ fs_test.c: In function 'layout0_ruleset_with_unknown_access': >> common.h:52:40: error: 'struct __test_metadata' has no member named 'step' 52 | _exit(_metadata->step); \ |^~ fs_test.c:592:1: note: in expansion of macro 'TEST_F_FORK' 592 | TEST_F_FORK(layout0, ruleset_with_unknown_access) | ^~~ common.h:58:34: error: 'struct __test_metadata' has no member named 'step' 58 | _metadata->
Re: [PATCH 1/3] selftests: lib.mk: Do not process TEST_GEN_MODS_DIR
Hi Marcos, kernel test robot noticed the following build errors: [auto build test ERROR on 345e8abe4c355bc24bab3f4a5634122e55be8665] url: https://github.com/intel-lab-lkp/linux/commits/Marcos-Paulo-de-Souza/selftests-lib-mk-Do-not-process-TEST_GEN_MODS_DIR/20240216-021601 base: 345e8abe4c355bc24bab3f4a5634122e55be8665 patch link: https://lore.kernel.org/r/20240215-lp-selftests-fixes-v1-1-89f4a6f5cddc%40suse.com patch subject: [PATCH 1/3] selftests: lib.mk: Do not process TEST_GEN_MODS_DIR compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240219/202402191417.xulh88ct-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202402191417.xulh88ct-...@intel.com/ All errors (new ones prefixed by >>): >> make[3]: *** /lib/modules/5.9.0-2-amd64/build: No such file or directory. >> Stop. -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/3] selftests: lib.mk: Simplify TEST_GEN_MODS_DIR handling
Hi Marcos, kernel test robot noticed the following build warnings: [auto build test WARNING on 345e8abe4c355bc24bab3f4a5634122e55be8665] url: https://github.com/intel-lab-lkp/linux/commits/Marcos-Paulo-de-Souza/selftests-lib-mk-Do-not-process-TEST_GEN_MODS_DIR/20240216-021601 base: 345e8abe4c355bc24bab3f4a5634122e55be8665 patch link: https://lore.kernel.org/r/20240215-lp-selftests-fixes-v1-2-89f4a6f5cddc%40suse.com patch subject: [PATCH 2/3] selftests: lib.mk: Simplify TEST_GEN_MODS_DIR handling compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240219/202402191502.dallsrz0-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202402191502.dallsrz0-...@intel.com/ All warnings (new ones prefixed by >>): >> Makefile:11: warning: overriding recipe for target 'all' >> ../lib.mk:62: warning: ignoring old recipe for target 'all' make[1]: *** [../lib.mk:62: all] Error 2 Makefile:65: warning: overriding recipe for target 'emit_tests' ../lib.mk:120: warning: ignoring old recipe for target 'emit_tests' make[1]: *** No targets. Stop. make[1]: *** No targets. Stop. make[1]: *** No targets. Stop. vim +/all +11 Makefile ^1da177e4c3f41 Linus Torvalds 2005-04-16 7 ^1da177e4c3f41 Linus Torvalds 2005-04-16 8 # *DOCUMENTATION* ^1da177e4c3f41 Linus Torvalds 2005-04-16 9 # To see a list of typical targets execute "make help" ^1da177e4c3f41 Linus Torvalds 2005-04-16 10 # More info can be located in ./README ^1da177e4c3f41 Linus Torvalds 2005-04-16 @11 # Comments in this file are targeted only to the developer, do not ^1da177e4c3f41 Linus Torvalds 2005-04-16 12 # expect to learn how to build the kernel reading this file. ^1da177e4c3f41 Linus Torvalds 2005-04-16 13 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[linux-next:master] BUILD REGRESSION 2d5c7b7eb345249cb34d42cbc2b97b4c57ea944e
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 2d5c7b7eb345249cb34d42cbc2b97b4c57ea944e Add linux-next specific files for 20240220 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202402210011.c42qmsp5-...@intel.com Error/Warning: (recently discovered and may have been fixed) arch/x86/entry/entry_fred.c:117:9: error: use of undeclared identifier 'POSTED_INTR_VECTOR' arch/x86/entry/entry_fred.c:118:9: error: use of undeclared identifier 'POSTED_INTR_WAKEUP_VECTOR' arch/x86/entry/entry_fred.c:119:9: error: use of undeclared identifier 'POSTED_INTR_NESTED_VECTOR' Unverified Error/Warning (likely false positive, please contact us if interested): mm/userfaultfd.c:740 mfill_atomic() warn: inconsistent returns '&ctx->map_changing_lock'. Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- alpha-randconfig-r062-20240220 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-randconfig-002-20240220 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-004-20240220 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-randconfig-r131-20240220 | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- csky-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-001-20240220 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- csky-randconfig-r113-20240220 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le64 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le64-degrades-to-integer | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- i386-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-buildonly-randconfig-001-20240220 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-002-20240220 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-012-20240220 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-013-20240220 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-063-20240220 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le64 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le64-degrades-to-integer | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- loongarch-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- loongarch-randconfig-001-20240220 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-mem
[linux-next:master] BUILD REGRESSION 4893c639cc3659cefaa675bf1e59f4e7571afb5c
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 4893c639cc3659cefaa675bf1e59f4e7571afb5c Add linux-next specific files for 20240221 Error/Warning: (recently discovered and may have been fixed) ld.lld: error: undefined symbol: ipt_alloc_initial_table ld.lld: error: undefined symbol: ipt_do_table ld.lld: error: undefined symbol: ipt_register_table ld.lld: error: undefined symbol: ipt_unregister_table_exit Unverified Error/Warning (likely false positive, please contact us if interested): fs/pidfs.c:98 pidfd_show_fdinfo() error: 'pid' dereferencing possible ERR_PTR() mm/userfaultfd.c:740 mfill_atomic() warn: inconsistent returns '&ctx->map_changing_lock'. Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- alpha-randconfig-r121-20240221 | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-randconfig-002-20240221 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm64-randconfig-003-20240221 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- csky-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-002-20240221 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-buildonly-randconfig-001-20240221 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-001-20240221 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-011-20240221 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-013-20240221 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-051-20240221 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-062-20240221 | |-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t | |-- sound-core-sound_kunit.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-restricted-snd_pcm_format_t-usertype-format-got-int | `-- sound-core-sound_kunit.c:sparse:sparse:restricted-snd_pcm_format_t-degrades-to-integer |-- i386-randconfig-141-20240221 | |-- drivers-bluetooth-btintel.c-btintel_read_version()-warn:passing-zero-to-PTR_ERR | `-- mm-page_owner.c-stack_print()-warn:unsigned-nr_entries-is-never-less-than-zero. |-- loongarch-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- loongarch-randconfig-r064-20240221 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- loongarch-randconfig-r111-20240221 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | |-- drivers-leds-flash-leds-ktd2692.c:sparse:sparse:symbol-ktd2692_timing-was-not-declared.-Should-it-be-static | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le64 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le32-deg
[linux-next:master] BUILD REGRESSION e31185ce00a96232308300008db193416ceb9769
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: e31185ce00a9623230838db193416ceb9769 Add linux-next specific files for 20240222 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/20240223.h9rfmyj4-...@intel.com https://lore.kernel.org/oe-kbuild-all/20240314.j6a7eb4b-...@intel.com https://lore.kernel.org/oe-kbuild-all/202402230537.2s6nhfsn-...@intel.com Error/Warning: (recently discovered and may have been fixed) arch/arm/boot/compressed/misc.c:157:6: warning: no previous prototype for function '__fortify_panic' [-Wmissing-prototypes] arch/arm/boot/compressed/misc.h:13:36: error: macro "fortify_panic" requires 2 arguments, but only 1 given arch/sh/boot/compressed/../../../../lib/decompress_unxz.c:350:(.text+0x20b4): undefined reference to `__ubsan_handle_out_of_bounds' sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/xz/xz_dec_lzma2.c:751:(.text+0x904): undefined reference to `__ubsan_handle_out_of_bounds' Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-randconfig-001-20240222 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arc-randconfig-002-20240222 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arc-randconfig-r122-20240223 | |-- drivers-video-backlight-ktd2801-backlight.c:sparse:sparse:symbol-ktd2801_timing-was-not-declared.-Should-it-be-static | |-- fs-ntfs3-frecord.c:warning:unused-variable-i_size | |-- fs-ntfs3-fslog.c:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le64 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le64-degrades-to-integer | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- arc-randconfig-r133-20240223 | |-- drivers-leds-flash-leds-ktd2692.c:sparse:sparse:symbol-ktd2692_timing-was-not-declared.-Should-it-be-static | |-- fs-ntfs3-frecord.c:warning:unused-variable-i_size | |-- fs-ntfs3-fslog.c:sparse:sparse:restricted-__le32-degrades-to-integer | |-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t | |-- sound-core-sound_kunit.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-restricted-snd_pcm_format_t-usertype-format-got-int | `-- sound-core-sound_kunit.c:sparse:sparse:restricted-snd_pcm_format_t-degrades-to-integer |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-aspeed_g5_defconfig | `-- arch-arm-boot-compressed-misc.h:error:macro-fortify_panic-requires-arguments-but-only-given |-- arm-multi_v7_defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-001-20240222 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm-tegra_defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-001-20240222 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-002-20240222 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-buildonly-randconfig-006-20240222 | `-- drivers-gpu-drm-nouveau-nv
[linux-next:master] BUILD REGRESSION 33e1d31873f87d119e5120b88cd350efa68ef276
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 33e1d31873f87d119e5120b88cd350efa68ef276 Add linux-next specific files for 20240223 Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arc-randconfig-r122-20240223 | |-- drivers-video-backlight-ktd2801-backlight.c:sparse:sparse:symbol-ktd2801_timing-was-not-declared.-Should-it-be-static | |-- fs-ntfs3-frecord.c:warning:unused-variable-i_size | |-- fs-ntfs3-fslog.c:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le64 | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le32-degrades-to-integer | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:restricted-__le64-degrades-to-integer | `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t |-- arc-randconfig-r133-20240223 | |-- drivers-leds-flash-leds-ktd2692.c:sparse:sparse:symbol-ktd2692_timing-was-not-declared.-Should-it-be-static | |-- fs-ntfs3-frecord.c:warning:unused-variable-i_size | |-- fs-ntfs3-fslog.c:sparse:sparse:restricted-__le32-degrades-to-integer | |-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t | |-- sound-core-sound_kunit.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-restricted-snd_pcm_format_t-usertype-format-got-int | `-- sound-core-sound_kunit.c:sparse:sparse:restricted-snd_pcm_format_t-degrades-to-integer |-- arm-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm-randconfig-004-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- arm-tegra_defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-defconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- arm64-randconfig-004-20240223 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- csky-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-001-20240223 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- csky-randconfig-002-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-allmodconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-allyesconfig | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-buildonly-randconfig-001-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-buildonly-randconfig-003-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-buildonly-randconfig-004-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-012-20240223 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg |-- i386-randconfig-054-20240223 | `-- fs-ntfs3-frecord.c:warning:unused-variable-i_size |-- i386-randconfig-061-20240223 | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | |-- drivers-video-backlight-ktd2801-backlight.c:sparse:sparse:symbol-ktd2801_timing-was-not-declared.-Should-it-be-static | |-- include-trace-..-..-drivers-bus-mhi-host-trace.h:sparse:sparse:cast-to-restricted-__le32 | |-- include-tr
[linux-next:master] [selftests/harness] 0710a1a73f: kernel-selftests.seccomp.seccomp_bpf.TRAP.dfl.fail
Hello,
kernel test robot noticed "kernel-selftests.seccomp.seccomp_bpf.TRAP.dfl.fail"
on:
commit: 0710a1a73fb45033ebb06073e374ab7d44a05f15 ("selftests/harness: Merge
TEST_F_FORK() into TEST_F()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 67908bf6954b7635d33760ff6dfc189fc26ccc89]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-4306b286-1_20240301
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
| Closes:
https://lore.kernel.org/oe-lkp/202403051529.cf359aed-oliver.s...@intel.com
in fact, we found more tests failed on this commit but can pass on parent:
e74048650eaff667 0710a1a73fb45033ebb06073e37
---
fail:runs %reproductionfail:runs
| | |
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_poke.read_has_side_effects.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.kill_after.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.kill_immediate.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.skip_after.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.syscall_allowed.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.syscall_errno.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.syscall_faked.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.ptrace.syscall_redirected.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.kill_after.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.kill_immediate.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.skip_after.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.syscall_allowed.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.syscall_errno.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.syscall_faked.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRACE_syscall.seccomp.syscall_redirected.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRAP.dfl.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.TRAP.ign.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.precedence.kill_is_highest.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.precedence.kill_is_highest_in_any_order.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.precedence.trap_is_second.fail
:6 100% 6:6
kernel-selftests.seccomp.seccomp_bpf.precedence.trap_is_second_in_any_order.fail
more details could be found in 'kernel-selftests' file in below link.
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240305/202403051529.cf359aed-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH bpf-next v2 6/9] bpf: tracing: add multi-link support
Hi Menglong,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Menglong-Dong/bpf-tracing-add-support-to-record-and-check-the-accessed-args/20240311-173954
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20240311093526.1010158-7-dongmenglong.8%40bytedance.com
patch subject: [PATCH bpf-next v2 6/9] bpf: tracing: add multi-link support
config: hexagon-allmodconfig
(https://download.01.org/0day-ci/archive/20240312/202403120218.me518ksk-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
503c55e17037436dcd45ac69dea8967e67e3f5e8)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240312/202403120218.me518ksk-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202403120218.me518ksk-...@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/bpf/syscall.c:4:
In file included from include/linux/bpf.h:31:
In file included from include/linux/memcontrol.h:13:
In file included from include/linux/cgroup.h:26:
In file included from include/linux/kernel_stat.h:9:
In file included from include/linux/interrupt.h:11:
In file included from include/linux/hardirq.h:11:
In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
In file included from include/asm-generic/hardirq.h:17:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/hexagon/include/asm/io.h:328:
include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE +
addr));
| ~~ ^
include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from
macro '__le32_to_cpu'
35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
| ^
In file included from kernel/bpf/syscall.c:4:
In file included from include/linux/bpf.h:31:
In file included from include/linux/memcontrol.h:13:
In file included from include/linux/cgroup.h:26:
In file included from include/linux/kernel_stat.h:9:
In file included from include/linux/interrupt.h:11:
In file included from include/linux/hardirq.h:11:
In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
In file included from include/asm-generic/hardirq.h:17:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/hexagon/include/asm/io.h:328:
include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
584 | __raw_writeb(value, PCI_IOBASE + addr);
| ~~ ^
include/asm-generic/io.h:594:59: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
594 | __raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE +
addr);
| ~~ ^
include/asm-generic/io.h:604:59: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
604 | __raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE +
addr);
| ~~ ^
In file included from kernel/bpf/syscall.c:4:
include/linux/bpf.h:751:48: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
751 | ARG_PTR_TO_MAP_VALUE_OR_NULL= PTR_MAYBE_NULL |
ARG_PTR_TO_MAP_VALUE,
| ~~ ^
include/linux/bpf.h:752:43: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
752 | ARG_PTR_TO_MEM_OR_NULL = PTR_MAYBE_NULL |
ARG_PTR_TO_MEM,
| ~~ ^
~~
include/linux/bpf.h:753:43: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
753
Re: [PATCH bpf-next v2 6/9] bpf: tracing: add multi-link support
Hi Menglong,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Menglong-Dong/bpf-tracing-add-support-to-record-and-check-the-accessed-args/20240311-173954
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20240311093526.1010158-7-dongmenglong.8%40bytedance.com
patch subject: [PATCH bpf-next v2 6/9] bpf: tracing: add multi-link support
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20240312/202403120515.lmaoytdg-...@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240312/202403120515.lmaoytdg-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202403120515.lmaoytdg-...@intel.com/
All errors (new ones prefixed by >>):
kernel/bpf/syscall.c: In function 'bpf_tracing_multi_link_release':
>> kernel/bpf/syscall.c:3538:9: error: implicit declaration of function
>> 'bpf_trampoline_multi_unlink_prog'; did you mean
>> 'bpf_trampoline_unlink_prog'? [-Werror=implicit-function-declaration]
3538 | bpf_trampoline_multi_unlink_prog(&multi_link->link);
| ^~~~
| bpf_trampoline_unlink_prog
kernel/bpf/syscall.c: In function 'bpf_tracing_prog_attach_multi':
>> kernel/bpf/syscall.c:3815:15: error: implicit declaration of function
>> 'bpf_trampoline_multi_link_prog'; did you mean 'bpf_trampoline_unlink_prog'?
>> [-Werror=implicit-function-declaration]
3815 | err = bpf_trampoline_multi_link_prog(&link->link);
| ^~
| bpf_trampoline_unlink_prog
cc1: some warnings being treated as errors
vim +3538 kernel/bpf/syscall.c
3532
3533 static void bpf_tracing_multi_link_release(struct bpf_link *link)
3534 {
3535 struct bpf_tracing_multi_link *multi_link =
3536 container_of(link, struct bpf_tracing_multi_link,
link.link);
3537
> 3538 bpf_trampoline_multi_unlink_prog(&multi_link->link);
3539 __bpf_tracing_multi_link_release(multi_link);
3540 }
3541
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [selftests/harness] 0710a1a73f: kernel-selftests.pidfd.pidfd_setns_test.fail
Hello,
kernel test robot noticed "kernel-selftests.pidfd.pidfd_setns_test.fail" on:
commit: 0710a1a73fb45033ebb06073e374ab7d44a05f15 ("selftests/harness: Merge
TEST_F_FORK() into TEST_F()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 4cece764965020c22cff7665b18a012006359095]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-4306b286-1_20240301
with following parameters:
group: pidfd
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
| Closes:
https://lore.kernel.org/oe-lkp/202403291015.1fcfa957-oliver.s...@intel.com
# timeout set to 300
# selftests: pidfd: pidfd_setns_test
# TAP version 13
# 1..7
# # Starting 7 tests from 2 test cases.
# # RUN global.setns_einval ...
# #OK global.setns_einval
# ok 1 global.setns_einval
# # RUN current_nsset.invalid_flags ...
# # pidfd_setns_test.c:161:invalid_flags:Expected self->child_pid_exited (0) >
0 (0)
# #OK current_nsset.invalid_flags
# ok 2 current_nsset.invalid_flags
# # RUN current_nsset.pidfd_exited_child ...
# # pidfd_setns_test.c:161:pidfd_exited_child:Expected self->child_pid_exited
(0) > 0 (0)
# #OK current_nsset.pidfd_exited_child
# ok 3 current_nsset.pidfd_exited_child
# # RUN current_nsset.pidfd_incremental_setns ...
# # pidfd_setns_test.c:161:pidfd_incremental_setns:Expected
self->child_pid_exited (0) > 0 (0)
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to user namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to mnt namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to pid namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to uts namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to ipc namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to net namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to cgroup namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:408:pidfd_incremental_setns:Managed to correctly setns
to pid_for_children namespace of 45423 via pidfd 20
# # pidfd_setns_test.c:391:pidfd_incremental_setns:Expected
setns(self->child_pidfd1, info->flag) (-1) == 0 (0)
# # pidfd_setns_test.c:392:pidfd_incremental_setns:Too many users - Failed to
setns to time namespace of 45423 via pidfd 20
# # pidfd_incremental_setns: Test terminated by timeout
# # FAIL current_nsset.pidfd_incremental_setns
# not ok 4 current_nsset.pidfd_incremental_setns
# # RUN current_nsset.nsfd_incremental_setns ...
# # pidfd_setns_test.c:161:nsfd_incremental_setns:Expected
self->child_pid_exited (0) > 0 (0)
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
user namespace of 45524 via nsfd 19
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
mnt namespace of 45524 via nsfd 24
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
pid namespace of 45524 via nsfd 27
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
uts namespace of 45524 via nsfd 30
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
ipc namespace of 45524 via nsfd 33
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
net namespace of 45524 via nsfd 36
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
cgroup namespace of 45524 via nsfd 39
# # pidfd_setns_test.c:444:nsfd_incremental_setns:Managed to correctly setns to
pid_for_children namespace of 45524 via nsfd 42
# # pidfd_setns_test.c:427:nsfd_incremental_setns:Expected
setns(self->child_nsfds1[i], info->flag) (-1) == 0 (0)
# # pidfd_setns_test.c:428:nsfd_incremental_setns:Too many users - Failed to
setns to time namespace of 45524 via nsfd 45
# # nsfd_incremental_setns: Test terminated by timeout
# # FAIL current_nsset.nsfd_incremental_setns
# not ok 5 current_nsset.nsfd_incremental_setns
# # RUN current_nsset.pidfd_one_shot_setns ...
# # pidfd_setns_test.c:161:pidfd_one_shot_setns:Expected self->child_pid_exited
(0) > 0 (0)
# # pidfd_setns_test.c:462:pidfd_one_shot_setns:Adding user namespace of 45630
to list of namespaces to attach to
# # pidfd_setns_test.c:462:pidfd_one_shot
[linus:master] [selftests] 58e2847ad2: kernel-selftests.openat2.resolve_test.fail
Hello,
kernel test robot noticed "kernel-selftests.openat2.resolve_test.fail" on:
commit: 58e2847ad2e6322a25dedf8b4549ff924baf8395 ("selftests: line buffer test
program's stdout")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 0bb80ecc33a8fb5a682236443c1e740d5c917d1d]
[test failed on linux-next/master 7bc675554773f09d88101bf1ccfc8537dc7c0be9]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: group-02
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
| Closes:
https://lore.kernel.org/oe-lkp/202309121342.97e2f008-oliver.s...@intel.com
besides kernel-selftests.openat2.resolve_test, we also observed
ea09800bf17561a0 58e2847ad2e6322a25dedf8b454
---
fail:runs %reproductionfail:runs
| | |
:6 100% 6:6
kernel-selftests.openat2.openat2_test.fail
:6 100% 6:6
kernel-selftests.openat2.resolve_test.fail
which pass on parent commit.
however, there are other tests such like below "perf_events: sigtrap_threads"
are not impacted by this commit.
we want to consult with you if there is some special config need to do after
this commit? Thanks a lot!
TAP version 13
1..3
# timeout set to 300
# selftests: openat2: openat2_test
# ==4052==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
not ok 1 selftests: openat2: openat2_test # exit=1
# timeout set to 300
# selftests: openat2: resolve_test
# ==4070==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
not ok 2 selftests: openat2: resolve_test # exit=1
...
TAP version 13
1..2
# timeout set to 120
# selftests: perf_events: sigtrap_threads
# TAP version 13
# 1..5
# # Starting 5 tests from 1 test cases.
# # RUN sigtrap_threads.remain_disabled ...
# #OK sigtrap_threads.remain_disabled
# ok 1 sigtrap_threads.remain_disabled
...
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230912/202309121342.97e2f008-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH V6 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion.
Hi Meng,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on tip/x86/core linus/master v6.6-rc1 next-20230912]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Meng-Li/x86-Drop-CPU_SUP_INTEL-from-SCHED_MC_PRIO-for-the-expansion/20230908-154939
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
patch link:
https://lore.kernel.org/r/20230908074653.2799055-2-li.meng%40amd.com
patch subject: [PATCH V6 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for
the expansion.
config: i386-buildonly-randconfig-004-20230913
(https://download.01.org/0day-ci/archive/20230913/202309130938.dmi2pwub-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20230913/202309130938.dmi2pwub-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202309130938.dmi2pwub-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/cpufreq/amd-pstate.c:41:
>> include/acpi/processor.h:226:9: error: unknown type name 'phys_cpuid_t'
226 | phys_cpuid_t phys_id; /* CPU hardware ID such as APIC ID
for x86 */
| ^~~~
include/acpi/processor.h:355:1: error: unknown type name 'phys_cpuid_t'
355 | phys_cpuid_t acpi_get_phys_id(acpi_handle, int type, u32 acpi_id);
| ^~~~
include/acpi/processor.h:356:1: error: unknown type name 'phys_cpuid_t'
356 | phys_cpuid_t acpi_map_madt_entry(u32 acpi_id);
| ^~~~
include/acpi/processor.h:357:20: error: unknown type name 'phys_cpuid_t'
357 | int acpi_map_cpuid(phys_cpuid_t phys_id, u32 acpi_id);
|^~~~
drivers/cpufreq/amd-pstate.c: In function
'amd_pstate_acpi_pm_profile_server':
drivers/cpufreq/amd-pstate.c:1076:17: error: 'acpi_gbl_FADT' undeclared
(first use in this function); did you mean 'acpi_table_fadt'?
1076 | switch (acpi_gbl_FADT.preferred_profile) {
| ^
| acpi_table_fadt
drivers/cpufreq/amd-pstate.c:1076:17: note: each undeclared identifier is
reported only once for each function it appears in
drivers/cpufreq/amd-pstate.c: In function
'amd_pstate_acpi_pm_profile_undefined':
drivers/cpufreq/amd-pstate.c:1087:13: error: 'acpi_gbl_FADT' undeclared
(first use in this function); did you mean 'acpi_table_fadt'?
1087 | if (acpi_gbl_FADT.preferred_profile == PM_UNSPECIFIED)
| ^
| acpi_table_fadt
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for X86_AMD_PSTATE
Depends on [n]: CPU_FREQ [=y] && X86 [=y] && ACPI [=n]
Selected by [y]:
- SCHED_MC_PRIO [=y] && SCHED_MC [=y] && CPU_SUP_AMD [=y]
WARNING: unmet direct dependencies detected for VIDEO_OV7640
Depends on [n]: MEDIA_SUPPORT [=y] && VIDEO_DEV [=y] && VIDEO_CAMERA_SENSOR
[=n]
Selected by [y]:
- VIDEO_GO7007 [=y] && MEDIA_SUPPORT [=y] && MEDIA_USB_SUPPORT [=y] &&
MEDIA_ANALOG_TV_SUPPORT [=y] && VIDEO_DEV [=y] && I2C [=y] && SND [=y] && USB
[=y] && MEDIA_SUBDRV_AUTOSELECT [=y] && MEDIA_CAMERA_SUPPORT [=y]
vim +/phys_cpuid_t +226 include/acpi/processor.h
^1da177e4c3f41 Linus Torvalds2005-04-16 222
^1da177e4c3f41 Linus Torvalds2005-04-16 223 struct acpi_processor {
^1da177e4c3f41 Linus Torvalds2005-04-16 224acpi_handle handle;
^1da177e4c3f41 Linus Torvalds2005-04-16 225u32 acpi_id;
828aef376d7a12 Catalin Marinas 2015-03-24 @226phys_cpuid_t phys_id;
/* CPU hardware ID such as APIC ID for x86 */
af8f3f514d193e Hanjun Guo2015-01-04 227u32 id; /* CPU
logical ID allocated by OS */
^1da177e4c3f41 Linus Torvalds2005-04-16 228u32 pblk;
^1da177e4c3f41 Linus Torvalds2005-04-16 229int
performance_platform_limit;
01854e697a77a4 Luming Yu 2007-05-26 230int
throttling_platform_limit;
ff55a9cebab024 Len Brown 2007-06-02 231/* 0 - states 0..n-th
state available */
01854e697a77a4 Luming Yu 2007-05-26 232
^1da177e4c3f41 Linus Torvalds2005-04-16 233struct
acpi_processor_flags flags;
^1da177e4c3f41 Li
Re: [PATCH 4/4] kunit: test: Fix the possible memory leak in executor_test
Hi Jinjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on next-20230914]
[cannot apply to v6.6-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/kunit-Fix-missed-memory-release-in-kunit_free_suite_set/20230914-194915
base: linus/master
patch link:
https://lore.kernel.org/r/20230914114629.1517650-5-ruanjinjie%40huawei.com
patch subject: [PATCH 4/4] kunit: test: Fix the possible memory leak in
executor_test
config: m68k-allyesconfig
(https://download.01.org/0day-ci/archive/20230914/202309142251.uj8saazv-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20230914/202309142251.uj8saazv-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202309142251.uj8saazv-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from lib/kunit/executor.c:353:
>> lib/kunit/executor_test.c:274:13: warning: 'kfree_at_end' defined but not
>> used [-Wunused-function]
274 | static void kfree_at_end(struct kunit *test, const void *to_free)
| ^~~~
vim +/kfree_at_end +274 lib/kunit/executor_test.c
1d71307a6f94df Daniel Latypov 2021-04-20 270
1d71307a6f94df Daniel Latypov 2021-04-20 271 /* Use the resource API to
register a call to kfree(to_free).
1d71307a6f94df Daniel Latypov 2021-04-20 272 * Since we never actually use
the resource, it's safe to use on const data.
1d71307a6f94df Daniel Latypov 2021-04-20 273 */
1d71307a6f94df Daniel Latypov 2021-04-20 @274 static void kfree_at_end(struct
kunit *test, const void *to_free)
1d71307a6f94df Daniel Latypov 2021-04-20 275 {
1d71307a6f94df Daniel Latypov 2021-04-20 276 /* kfree() handles NULL
already, but avoid allocating a no-op cleanup. */
1d71307a6f94df Daniel Latypov 2021-04-20 277 if (IS_ERR_OR_NULL(to_free))
1d71307a6f94df Daniel Latypov 2021-04-20 278 return;
00e63f8afcfc6b David Gow 2023-05-25 279
00e63f8afcfc6b David Gow 2023-05-25 280 kunit_add_action(test,
00e63f8afcfc6b David Gow 2023-05-25 281 (kunit_action_t
*)kfree,
1d71307a6f94df Daniel Latypov 2021-04-20 282 (void
*)to_free);
1d71307a6f94df Daniel Latypov 2021-04-20 283 }
1d71307a6f94df Daniel Latypov 2021-04-20 284
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/2] selftests: kvm: remove print_skip()
Hi Muhammad,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kvm/queue]
[also build test WARNING on kvmarm/next kvms390/next linus/master v6.10-rc3
next-20240613]
[cannot apply to kvm/linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Muhammad-Usama-Anjum/selftests-kvm-replace-exit-with-ksft_exit_fail_msg/20240612-184820
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link:
https://lore.kernel.org/r/20240612104500.425012-1-usama.anjum%40collabora.com
patch subject: [PATCH 1/2] selftests: kvm: remove print_skip()
:: branch date: 3 days ago
:: commit date: 3 days ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240615/202406151641.bjql765q-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202406151641.bjql765q-...@intel.com/
All warnings (new ones prefixed by >>):
>> x86_64/hyperv_cpuid.c:155:1: warning: unused label 'do_sys' [-Wunused-label]
155 | do_sys:
| ^~~
>> x86_64/hyperv_cpuid.c:165:1: warning: unused label 'out' [-Wunused-label]
165 | out:
| ^~~~
2 warnings generated.
vim +/do_sys +155 tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
7edcb73433276d Vitaly Kuznetsov 2018-12-10 128
7edcb73433276d Vitaly Kuznetsov 2018-12-10 129 int main(int argc, char
*argv[])
7edcb73433276d Vitaly Kuznetsov 2018-12-10 130 {
7edcb73433276d Vitaly Kuznetsov 2018-12-10 131 struct kvm_vm *vm;
813e38cd6d7b42 Sean Christopherson 2022-06-14 132 const struct kvm_cpuid2
*hv_cpuid_entries;
5c6e31b3bc4b52 Sean Christopherson 2022-02-15 133 struct kvm_vcpu *vcpu;
7edcb73433276d Vitaly Kuznetsov 2018-12-10 134
7ed397d107d461 Sean Christopherson 2022-05-27 135
TEST_REQUIRE(kvm_has_cap(KVM_CAP_HYPERV_CPUID));
7edcb73433276d Vitaly Kuznetsov 2018-12-10 136
5c6e31b3bc4b52 Sean Christopherson 2022-02-15 137 vm =
vm_create_with_one_vcpu(&vcpu, guest_code);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 138
8b460692fee46a Vitaly Kuznetsov 2020-09-29 139 /* Test vCPU ioctl
version */
5c6e31b3bc4b52 Sean Christopherson 2022-02-15 140 test_hv_cpuid_e2big(vm,
vcpu);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 141
768e9a61856b75 Sean Christopherson 2022-06-02 142 hv_cpuid_entries =
vcpu_get_supported_hv_cpuid(vcpu);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 143
test_hv_cpuid(hv_cpuid_entries, false);
813e38cd6d7b42 Sean Christopherson 2022-06-14 144 free((void
*)hv_cpuid_entries);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 145
1ecbb337fa107c Sean Christopherson 2022-06-14 146 if
(!kvm_cpu_has(X86_FEATURE_VMX) ||
a9af8b5d3d419a Muhammad Usama Anjum 2024-06-12 147
!kvm_has_cap(KVM_CAP_HYPERV_ENLIGHTENED_VMCS))
a9af8b5d3d419a Muhammad Usama Anjum 2024-06-12 148
ksft_exit_skip("Enlightened VMCS is unsupported\n");
a9af8b5d3d419a Muhammad Usama Anjum 2024-06-12 149
768e9a61856b75 Sean Christopherson 2022-06-02 150 vcpu_enable_evmcs(vcpu);
768e9a61856b75 Sean Christopherson 2022-06-02 151 hv_cpuid_entries =
vcpu_get_supported_hv_cpuid(vcpu);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 152
test_hv_cpuid(hv_cpuid_entries, true);
813e38cd6d7b42 Sean Christopherson 2022-06-14 153 free((void
*)hv_cpuid_entries);
8b460692fee46a Vitaly Kuznetsov 2020-09-29 154
8b460692fee46a Vitaly Kuznetsov 2020-09-29 @155 do_sys:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 4/4] selftests: ALSA: Cover userspace-driven timers with test
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tiwai-sound/for-next]
[also build test WARNING on tiwai-sound/for-linus linus/master v6.10
next-20240726]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/ALSA-aloop-Allow-using-global-timers/20240726-155158
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
patch link:
https://lore.kernel.org/r/20240726074750.626671-5-ivan.orlov0322%40gmail.com
patch subject: [PATCH 4/4] selftests: ALSA: Cover userspace-driven timers with
test
:: branch date: 2 days ago
:: commit date: 2 days ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240728/202407281359.vmydesrt-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202407281359.vmydesrt-...@intel.com/
All warnings (new ones prefixed by >>):
>> utimer-test.c:73:1: warning: non-void function does not return a value
>> [-Wreturn-type]
73 | }
| ^
>> utimer-test.c:117:11: warning: enumeration value 'TIMER_NO_EVENT' not
>> handled in switch [-Wswitch]
117 | switch (parse_timer_output(buf)) {
| ^~~
2 warnings generated.
vim +73 tools/testing/selftests/alsa/utimer-test.c
5cf58530fa628b Ivan Orlov 2024-07-26 62
5cf58530fa628b Ivan Orlov 2024-07-26 63 static void *ticking_func(void *data)
5cf58530fa628b Ivan Orlov 2024-07-26 64 {
5cf58530fa628b Ivan Orlov 2024-07-26 65int i;
5cf58530fa628b Ivan Orlov 2024-07-26 66int *fd = (int *)data;
5cf58530fa628b Ivan Orlov 2024-07-26 67
5cf58530fa628b Ivan Orlov 2024-07-26 68for (i = 0; i < TICKS_COUNT;
i++) {
5cf58530fa628b Ivan Orlov 2024-07-26 69/* Well, trigger the
timer! */
5cf58530fa628b Ivan Orlov 2024-07-26 70ioctl(*fd,
SNDRV_TIMER_IOCTL_TRIGGER, NULL);
5cf58530fa628b Ivan Orlov 2024-07-26 71sleep(TIMER_FREQ_SEC);
5cf58530fa628b Ivan Orlov 2024-07-26 72}
5cf58530fa628b Ivan Orlov 2024-07-26 @73 }
5cf58530fa628b Ivan Orlov 2024-07-26 74
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/4] ALSA: timer: Introduce virtual userspace-driven timers
Hi Ivan, kernel test robot noticed the following build warnings: [auto build test WARNING on tiwai-sound/for-next] [also build test WARNING on tiwai-sound/for-linus linus/master v6.11-rc1 next-20240729] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/ALSA-aloop-Allow-using-global-timers/20240729-171015 base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next patch link: https://lore.kernel.org/r/20240729085905.6602-4-ivan.orlov0322%40gmail.com patch subject: [PATCH v2 3/4] ALSA: timer: Introduce virtual userspace-driven timers config: nios2-randconfig-r113-20240730 (https://download.01.org/0day-ci/archive/20240730/202407301002.saobm0na-...@intel.com/config) compiler: nios2-linux-gcc (GCC) 14.1.0 reproduce: (https://download.01.org/0day-ci/archive/20240730/202407301002.saobm0na-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202407301002.saobm0na-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> sound/core/timer.c:2030:1: sparse: sparse: symbol 'snd_utimer_ids' was not >> declared. Should it be static? sound/core/timer.c:230:12: sparse: sparse: context imbalance in 'check_matching_master_slave' - different lock contexts for basic block sound/core/timer.c:405:9: sparse: sparse: context imbalance in 'remove_slave_links' - wrong count at exit sound/core/timer.c:456:9: sparse: sparse: context imbalance in 'snd_timer_close_locked' - wrong count at exit sound/core/timer.c:492:15: sparse: sparse: context imbalance in 'snd_timer_resolution' - different lock contexts for basic block sound/core/timer.c:541:12: sparse: sparse: context imbalance in 'snd_timer_start1' - wrong count at exit sound/core/timer.c:596:12: sparse: sparse: context imbalance in 'snd_timer_start_slave' - wrong count at exit sound/core/timer.c:616:12: sparse: sparse: context imbalance in 'snd_timer_stop1' - wrong count at exit sound/core/timer.c:673:9: sparse: sparse: context imbalance in 'snd_timer_stop_slave' - wrong count at exit sound/core/timer.c:780:25: sparse: sparse: context imbalance in 'snd_timer_process_callbacks' - unexpected unlock sound/core/timer.c:798:9: sparse: sparse: context imbalance in 'snd_timer_clear_callbacks' - wrong count at exit sound/core/timer.c:806:13: sparse: sparse: context imbalance in 'snd_timer_work' - different lock contexts for basic block sound/core/timer.c:825:6: sparse: sparse: context imbalance in 'snd_timer_interrupt' - different lock contexts for basic block sound/core/timer.c:1049:6: sparse: sparse: context imbalance in 'snd_timer_notify' - different lock contexts for basic block sound/core/timer.c:1323:9: sparse: sparse: context imbalance in 'snd_timer_user_interrupt' - wrong count at exit sound/core/timer.c:1430:12: sparse: sparse: context imbalance in 'realloc_user_queue' - wrong count at exit sound/core/timer.c:1672:12: sparse: sparse: context imbalance in 'snd_timer_user_gstatus' - different lock contexts for basic block sound/core/timer.c:2412:9: sparse: sparse: context imbalance in 'snd_timer_user_poll' - wrong count at exit vim +/snd_utimer_ids +2030 sound/core/timer.c 2024 2025 #ifdef CONFIG_SND_UTIMER 2026 /* 2027 * Since userspace-driven timers are passed to userspace, we need to have an identifier 2028 * which will allow us to use them (basically, the subdevice number of udriven timer). 2029 */ > 2030 DEFINE_IDA(snd_utimer_ids); 2031 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 06/19] riscv: Extend cpufeature.c to detect vendor extensions
Hi Charlie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 4cece764965020c22cff7665b18a012006359095]
url:
https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/dt-bindings-riscv-Add-vendorid-and-archid/20240412-121709
base: 4cece764965020c22cff7665b18a012006359095
patch link:
https://lore.kernel.org/r/20240411-dev-charlie-support_thead_vector_6_9-v1-6-4af9815ec746%40rivosinc.com
patch subject: [PATCH 06/19] riscv: Extend cpufeature.c to detect vendor
extensions
config: riscv-defconfig
(https://download.01.org/0day-ci/archive/20240412/202404122206.tkxkhj29-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
8b3b4a92adee40483c27f26c478a384cd69c6f05)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240412/202404122206.tkxkhj29-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202404122206.tkxkhj29-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/riscv/kernel/cpufeature.c:20:
In file included from arch/riscv/include/asm/cacheflush.h:9:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> arch/riscv/kernel/cpufeature.c:395:4: warning: label followed by a
>> declaration is a C23 extension [-Wc23-extensions]
395 | bool found;
| ^
2 warnings generated.
vim +395 arch/riscv/kernel/cpufeature.c
370
371 static void __init riscv_parse_isa_string(unsigned long *this_hwcap,
struct riscv_isainfo *isainfo,
372 struct riscv_isainfo
*isavendorinfo, unsigned long vendorid,
373 unsigned long *isa2hwcap, const
char *isa)
374 {
375 /*
376 * For all possible cpus, we have already validated in
377 * the boot process that they at least contain "rv" and
378 * whichever of "32"/"64" this kernel supports, and so this
379 * section can be skipped.
380 */
381 isa += 4;
382
383 while (*isa) {
384 const char *ext = isa++;
385 const char *ext_end = isa;
386 bool ext_long = false, ext_err = false;
387 struct riscv_isainfo *selected_isainfo = isainfo;
388 const struct riscv_isa_ext_data *selected_riscv_isa_ext
= riscv_isa_ext;
389 size_t selected_riscv_isa_ext_count =
riscv_isa_ext_count;
390 unsigned int id_offset = 0;
391
392 switch (*ext) {
393 case 'x':
394 case 'X':
> 395 bool found;
396
397 found = get_isa_vendor_ext(vendorid,
398
&selected_riscv_isa_ext,
399
&selected_riscv_isa_ext_count);
400 selected_isainfo = isavendorinfo;
401 id_offset = RISCV_ISA_VENDOR_EXT_BASE;
402 if (!found) {
403 pr_warn("No associated vendor
extensions with vendor id: %lx\n",
404 vendorid);
405 for (; *isa && *isa != '_'; ++isa)
406 ;
407 ext_err = true;
408 break;
409 }
410 fallthrough;
411 case 's':
412 /*
413 * Workaround for invalid single-letter 's' &
'u' (QEMU).
414 * No need to set the bit in riscv_isa as 's' &
'u' are
415 * not valid ISA extensions. It works unless
the first
416 * multi-letter extension in the ISA string
begins with
417 * "Su" and is not prefixed with an underscore.
418 */
419 if (ext[-1] != '_&#
Re: [PATCH 06/19] riscv: Extend cpufeature.c to detect vendor extensions
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4cece764965020c22cff7665b18a012006359095]
url:
https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins/dt-bindings-riscv-Add-vendorid-and-archid/20240412-121709
base: 4cece764965020c22cff7665b18a012006359095
patch link:
https://lore.kernel.org/r/20240411-dev-charlie-support_thead_vector_6_9-v1-6-4af9815ec746%40rivosinc.com
patch subject: [PATCH 06/19] riscv: Extend cpufeature.c to detect vendor
extensions
config: riscv-randconfig-r133-20240413
(https://download.01.org/0day-ci/archive/20240414/202404140621.x9b02ef8-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce:
(https://download.01.org/0day-ci/archive/20240414/202404140621.x9b02ef8-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202404140621.x9b02ef8-...@intel.com/
All errors (new ones prefixed by >>):
>> arch/riscv/kernel/cpufeature.c:395:4: error: expected expression
395 | bool found;
| ^
>> arch/riscv/kernel/cpufeature.c:397:4: error: use of undeclared identifier
>> 'found'
397 | found = get_isa_vendor_ext(vendorid,
| ^
arch/riscv/kernel/cpufeature.c:402:9: error: use of undeclared identifier
'found'
402 | if (!found) {
| ^
3 errors generated.
vim +395 arch/riscv/kernel/cpufeature.c
370
371 static void __init riscv_parse_isa_string(unsigned long *this_hwcap,
struct riscv_isainfo *isainfo,
372 struct riscv_isainfo
*isavendorinfo, unsigned long vendorid,
373 unsigned long *isa2hwcap, const
char *isa)
374 {
375 /*
376 * For all possible cpus, we have already validated in
377 * the boot process that they at least contain "rv" and
378 * whichever of "32"/"64" this kernel supports, and so this
379 * section can be skipped.
380 */
381 isa += 4;
382
383 while (*isa) {
384 const char *ext = isa++;
385 const char *ext_end = isa;
386 bool ext_long = false, ext_err = false;
387 struct riscv_isainfo *selected_isainfo = isainfo;
388 const struct riscv_isa_ext_data *selected_riscv_isa_ext
= riscv_isa_ext;
389 size_t selected_riscv_isa_ext_count =
riscv_isa_ext_count;
390 unsigned int id_offset = 0;
391
392 switch (*ext) {
393 case 'x':
394 case 'X':
> 395 bool found;
396
> 397 found = get_isa_vendor_ext(vendorid,
398
&selected_riscv_isa_ext,
399
&selected_riscv_isa_ext_count);
400 selected_isainfo = isavendorinfo;
401 id_offset = RISCV_ISA_VENDOR_EXT_BASE;
402 if (!found) {
403 pr_warn("No associated vendor
extensions with vendor id: %lx\n",
404 vendorid);
405 for (; *isa && *isa != '_'; ++isa)
406 ;
407 ext_err = true;
408 break;
409 }
410 fallthrough;
411 case 's':
412 /*
413 * Workaround for invalid single-letter 's' &
'u' (QEMU).
414 * No need to set the bit in riscv_isa as 's' &
'u' are
415 * not valid ISA extensions. It works unless
the first
416 * multi-letter extension in the ISA string
begins with
417 * "Su" and is not prefixed with an underscore.
418 */
419 if (ext[-1] != '_' && ext[1] == 'u') {
420 ++isa;
421 ext_err = true;
422
[linux-next:master] [kunit] 9353399610: kunit.VCAP_API_DebugFS_Testsuite.vcap_api_show_admin_raw_test.fail
Hello,
kernel test robot noticed
"kunit.VCAP_API_DebugFS_Testsuite.vcap_api_show_admin_raw_test.fail" on:
commit: 93533996100c60ea6d4342c454752c0eb1e4b6b1 ("kunit: Handle test faults")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 9ed46da14b9b9b2ad4edb3b0c545b6dbe5c00d39]
in testcase: kunit
version:
with following parameters:
group: group-03
compiler: gcc-13
test machine: 16 threads 1 sockets Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz
(Broadwell-DE) with 48G 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
| Closes: https://lore.kernel.org/oe-lkp/202404151340.5b152d96-...@intel.com
[ 206.153880][ T2978] # vcap_api_show_admin_raw_test: EXPECTATION FAILED
at drivers/net/ethernet/microchip/vcap/vcap_api_debugfs_kunit.c:377
[ 206.153880][ T2978] Expected test_expected == test_pr_buffer[0], but
[ 206.153880][ T2978] test_expected == " addr: 786, X6 rule, keysets:
VCAP_KFS_MAC_ETYPE
[ 206.153880][ T2978] "
[ 206.153880][ T2978] test_pr_buffer[0] == ""
[ 206.159902][T1] not ok 2 vcap_api_show_admin_raw_test
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240415/202404151340.5b152d96-...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/3] bpf: do not walk twice the hash map on free
Hi Benjamin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 52578f7f53ff8fe3a8f6f3bc8b5956615c07a16e]
url:
https://github.com/intel-lab-lkp/linux/commits/Benjamin-Tissoires/bpf-do-not-walk-twice-the-map-on-free/20240425-220322
base: 52578f7f53ff8fe3a8f6f3bc8b5956615c07a16e
patch link:
https://lore.kernel.org/r/20240425-bpf-next-v1-2-1d8330e6c643%40kernel.org
patch subject: [PATCH 2/3] bpf: do not walk twice the hash map on free
config: arc-randconfig-002-20240426
(https://download.01.org/0day-ci/archive/20240426/202404260653.ulrcgrp2-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240426/202404260653.ulrcgrp2-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202404260653.ulrcgrp2-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/hashtab.c:243:13: warning: 'htab_free_prealloced_wq' defined but
>> not used [-Wunused-function]
243 | static void htab_free_prealloced_wq(struct bpf_htab *htab)
| ^~~
vim +/htab_free_prealloced_wq +243 kernel/bpf/hashtab.c
68134668c17f31 Alexei Starovoitov 2021-07-14 242
246331e3f1eac9 Benjamin Tissoires 2024-04-20 @243 static void
htab_free_prealloced_wq(struct bpf_htab *htab)
246331e3f1eac9 Benjamin Tissoires 2024-04-20 244 {
246331e3f1eac9 Benjamin Tissoires 2024-04-20 245 u32 num_entries =
htab->map.max_entries;
246331e3f1eac9 Benjamin Tissoires 2024-04-20 246 int i;
246331e3f1eac9 Benjamin Tissoires 2024-04-20 247
246331e3f1eac9 Benjamin Tissoires 2024-04-20 248 if
(!btf_record_has_field(htab->map.record, BPF_WORKQUEUE))
246331e3f1eac9 Benjamin Tissoires 2024-04-20 249 return;
246331e3f1eac9 Benjamin Tissoires 2024-04-20 250 if
(htab_has_extra_elems(htab))
246331e3f1eac9 Benjamin Tissoires 2024-04-20 251 num_entries +=
num_possible_cpus();
246331e3f1eac9 Benjamin Tissoires 2024-04-20 252
246331e3f1eac9 Benjamin Tissoires 2024-04-20 253 for (i = 0; i <
num_entries; i++) {
246331e3f1eac9 Benjamin Tissoires 2024-04-20 254 struct
htab_elem *elem;
246331e3f1eac9 Benjamin Tissoires 2024-04-20 255
246331e3f1eac9 Benjamin Tissoires 2024-04-20 256 elem =
get_htab_elem(htab, i);
246331e3f1eac9 Benjamin Tissoires 2024-04-20 257
bpf_obj_free_workqueue(htab->map.record,
246331e3f1eac9 Benjamin Tissoires 2024-04-20 258
elem->key + round_up(htab->map.key_size, 8));
246331e3f1eac9 Benjamin Tissoires 2024-04-20 259 cond_resched();
246331e3f1eac9 Benjamin Tissoires 2024-04-20 260 }
246331e3f1eac9 Benjamin Tissoires 2024-04-20 261 }
246331e3f1eac9 Benjamin Tissoires 2024-04-20 262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [selftests/harness] 8092162335: kernel-selftests.sgx.make.fail
Hello,
kernel test robot noticed "kernel-selftests.sgx.make.fail" on:
commit: 8092162335554c8ef5e7f50eff68aa9cfbdbf865 ("selftests/harness: remove
use of LINE_MAX")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 98369dccd2f8e16bf4c6621053af7aa4821dcf8e]
[test failed on linux-next/master b0a2c79c6f3590b74742cbbc76687014d47972d8]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-c7864053-1_20240419
with following parameters:
group: sgx
compiler: gcc-13
test machine: 16 threads 1 sockets Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz
(Coffee 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
| Closes:
https://lore.kernel.org/oe-lkp/202404301040.3bea5782-oliver.s...@intel.com
KERNEL SELFTESTS: linux_headers_dir is
/usr/src/linux-headers-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865
2024-04-29 15:02:59 ln -sf /usr/sbin/iptables-nft /usr/bin/iptables
2024-04-29 15:02:59 ln -sf /usr/sbin/ip6tables-nft /usr/bin/ip6tables
2024-04-29 15:02:59 sed -i s/default_timeout=45/default_timeout=300/
kselftest/runner.sh
2024-04-29 15:02:59 make -j16 -C sgx
make: Entering directory
'/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx'
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c main.c -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/main.o
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c load.c -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/load.o
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c sigstruct.c -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/sigstruct.o
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c call.S -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/call.o
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c sign_key.S -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/sign_key.o
gcc -Wall -Werror -static-pie -nostdlib -ffreestanding -fPIE
-fno-stack-protector -mrdrnd
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
test_encl.c test_encl_bootstrap.S -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/test_encl.elf
-Wl,-T,test_encl.lds,--build-id=none
/usr/bin/ld: warning: /tmp/lkp/cct4g3SV.o: missing .note.GNU-stack section
implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
In file included from main.c:21:
../kselftest_harness.h: In function ‘__run_test’:
../kselftest_harness.h:1166:13: error: implicit declaration of function
‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
1166 | if (asprintf(&test_name, "%s%s%s.%s", f->name,
| ^~~~
| vsprintf
cc1: all warnings being treated as errors
make: *** [Makefile:36:
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx/main.o]
Error 1
make: Leaving directory
'/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx'
2024-04-29 15:03:00 make quicktest=1 run_tests -C sgx
make: Entering directory
'/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/sgx'
gcc -Wall -Werror -g
-I/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865/tools/testing/selftests/../../../tools/include
-fPIC -c main.c -o
/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-8092162335554c8ef5e7f50eff68aa9cfbdbf865
[linux-next:master] BUILD REGRESSION 93a39e4766083050ca0ecd6a3548093a3b9eb60c
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 93a39e4766083050ca0ecd6a3548093a3b9eb60c Add linux-next specific
files for 20240507
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202405080133.16zi5eay-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202405080300.itzpe1xh-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202405080553.tfh9ems8-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202405080801.qqazymz6-...@intel.com
Error/Warning: (recently discovered and may have been fixed)
/usr/bin/ld: drivers/net/dsa/realtek/rtl8366rb.c:980:(.text+0x2808): undefined
reference to `devm_led_classdev_register_ext'
ERROR: modpost: "drm_dsc_pps_payload_pack"
[drivers/gpu/drm/panel/panel-lg-sw43408.ko] undefined!
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:320:(.text+0x850): undefined
reference to `kunit_binary_assert_format'
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:322:(.text+0x734): undefined
reference to `kunit_mem_assert_format'
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:58:(.text+0x5ec): undefined
reference to `kunit_binary_ptr_assert_format'
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:58:(.text+0x60c): undefined
reference to `__kunit_abort'
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:77:(.text+0x5a0): undefined
reference to `kunit_unary_assert_format'
aarch64-linux-ld:
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:77:(.text+0x5b0): undefined
reference to `__kunit_do_failed_assertion'
csky-linux-ld: panel-lg-sw43408.c:(.text+0x310): undefined reference to
`drm_dsc_pps_payload_pack'
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1734:62: error: bitwise operation
between different enumeration types ('enum amd_asic_type' and 'enum
amd_chip_flags') [-Werror,-Wenum-enum-conversion]
drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c:723:42: error: arithmetic between
different enumeration types ('enum amdgpu_ras_block' and 'enum
amdgpu_ras_mca_block') [-Werror,-Wenum-enum-conversion]
drivers/gpu/drm/arm/display/komeda/komeda_dev.c:26:37: error: invalid use of
undefined type 'struct seq_file'
drivers/gpu/drm/arm/display/komeda/komeda_dev.c:29:9: error: implicit
declaration of function 'seq_puts' [-Werror=implicit-function-declaration]
drivers/gpu/drm/arm/display/komeda/komeda_dev.c:44:1: error: type defaults to
'int' in declaration of 'DEFINE_SHOW_ATTRIBUTE' [-Werror=implicit-int]
drivers/gpu/drm/drm_mm.c:614:20: error: function 'drm_mm_node_scanned_block' is
not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration]
drivers/gpu/drm/imx/ipuv3/imx-ldb.c:658:57: error: '_sel' directive output may
be truncated writing 4 bytes into a region of size between 3 and 13
[-Werror=format-truncation=]
drivers/gpu/drm/nouveau/nouveau_backlight.c:56:69: error: '%d' directive output
may be truncated writing between 1 and 10 bytes into a region of size 3
[-Werror=format-truncation=]
drivers/gpu/drm/nouveau/nvif/object.c:161:9: error: 'memcpy' accessing
4294967264 or more bytes at offsets 0 and 32 overlaps 6442450881 bytes at
offset -2147483617 [-Werror=restrict]
drivers/gpu/drm/pl111/pl111_versatile.c:488:24: error: cast to smaller integer
type 'enum versatile_clcd' from 'const void *'
[-Werror,-Wvoid-pointer-to-enum-cast]
drivers/gpu/drm/radeon/radeon_drv.c:251:2: error: bitwise operation between
different enumeration types ('enum radeon_family' and 'enum radeon_chip_flags')
[-Werror,-Wenum-enum-conversion]
drivers/gpu/drm/renesas/rcar-du/rcar_cmm.c:35:19: error: unused function
'rcar_cmm_read' [-Werror,-Wunused-function]
drivers/gpu/drm/xlnx/zynqmp_disp.c:949:14: error: logical not is only applied
to the left hand side of this comparison [-Werror,-Wlogical-not-parentheses]
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:322:(.text+0x728): undefined
reference to `kunit_mem_assert_format'
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:77:(.text+0x598): dangerous
relocation: unsupported relocation
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-test.c:77:(.text+0x598): undefined
reference to `kunit_unary_assert_format'
include/asm-generic/io.h:547:31: error: performing pointer arithmetic on a null
pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
include/kunit/test.h:444:(.text+0x440): undefined reference to
`kunit_kmalloc_array'
kernel/bpf/verifier.c:20086:85: error: 'pcpu_hot' undeclared (first use in this
function)
ld.lld: error: undefined symbol: drm_dsc_pps_payload_pack
panel-lg-sw43408.c:(.text+0x278): undefined reference to
`drm_dsc_pps_payload_pack'
panel-lg-sw43408.c:(.text+0x934): undefined reference to
`.drm_dsc_pps_payload_pack'
Unverified Error/Warning (likely false positive, please contact us if
interested):
drivers/net/dsa/realtek/rtl8366rb.c:1032:4-15: ERROR: probable double put.
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
|-- arc-allmodconfig
|
Re: [PATCH v2] kunit: Cover 'assert.c' with tests
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/kunit]
[also build test WARNING on linus/master v6.9-rc7 next-20240508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/kunit-Cover-assert-c-with-tests/20240508-212654
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit
patch link:
https://lore.kernel.org/r/20240508132557.599213-1-ivan.orlov0322%40gmail.com
patch subject: [PATCH v2] kunit: Cover 'assert.c' with tests
config: x86_64-randconfig-121-20240509
(https://download.01.org/0day-ci/archive/20240509/202405091128.rh6is2he-...@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project
e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240509/202405091128.rh6is2he-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202405091128.rh6is2he-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/kunit/assert_test.c:368:19: sparse: sparse: symbol 'assert_test_cases'
>> was not declared. Should it be static?
>> lib/kunit/assert_test.c:383:20: sparse: sparse: symbol 'assert_test_suite'
>> was not declared. Should it be static?
vim +/assert_test_cases +368 lib/kunit/assert_test.c
367
> 368 struct kunit_case assert_test_cases[] = {
369 KUNIT_CASE(kunit_test_is_literal),
370 KUNIT_CASE(kunit_test_is_str_literal),
371 KUNIT_CASE(kunit_test_assert_prologue),
372 KUNIT_CASE(kunit_test_assert_print_msg),
373 KUNIT_CASE(kunit_test_unary_assert_format),
374 KUNIT_CASE(kunit_test_ptr_not_err_assert_format),
375 KUNIT_CASE(kunit_test_binary_assert_format),
376 KUNIT_CASE(kunit_test_binary_ptr_assert_format),
377 KUNIT_CASE(kunit_test_binary_str_assert_format),
378 KUNIT_CASE(kunit_test_assert_hexdump),
379 KUNIT_CASE(kunit_test_mem_assert_format),
380 {}
381 };
382
> 383 struct kunit_suite assert_test_suite = {
384 .name = "kunit-assert",
385 .test_cases = assert_test_cases,
386 };
387
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] kunit: Cover 'assert.c' with tests
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/kunit]
[also build test WARNING on shuah-kselftest/kunit-fixes linus/master v6.9-rc7
next-20240508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/kunit-Cover-assert-c-with-tests/20240508-212654
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit
patch link:
https://lore.kernel.org/r/20240508132557.599213-1-ivan.orlov0322%40gmail.com
patch subject: [PATCH v2] kunit: Cover 'assert.c' with tests
config: i386-randconfig-001-20240509
(https://download.01.org/0day-ci/archive/20240509/202405091253.frha2zbi-...@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project
e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240509/202405091253.frha2zbi-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202405091253.frha2zbi-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/kunit/assert.c:35:6: warning: no previous prototype for function
>> 'kunit_assert_print_msg' [-Wmissing-prototypes]
35 | void kunit_assert_print_msg(const struct va_format *message,
| ^
lib/kunit/assert.c:35:1: note: declare 'static' if the function is not
intended to be used outside of this translation unit
35 | void kunit_assert_print_msg(const struct va_format *message,
| ^
| static
>> lib/kunit/assert.c:95:23: warning: no previous prototype for function
>> 'is_literal' [-Wmissing-prototypes]
95 | VISIBLE_IF_KUNIT bool is_literal(const char *text, long long value)
| ^
lib/kunit/assert.c:95:18: note: declare 'static' if the function is not
intended to be used outside of this translation unit
95 | VISIBLE_IF_KUNIT bool is_literal(const char *text, long long value)
| ^
| static
>> lib/kunit/assert.c:173:23: warning: no previous prototype for function
>> 'is_str_literal' [-Wmissing-prototypes]
173 | VISIBLE_IF_KUNIT bool is_str_literal(const char *text, const char
*value)
| ^
lib/kunit/assert.c:173:18: note: declare 'static' if the function is not
intended to be used outside of this translation unit
173 | VISIBLE_IF_KUNIT bool is_str_literal(const char *text, const char
*value)
| ^
| static
>> lib/kunit/assert.c:217:6: warning: no previous prototype for function
>> 'kunit_assert_hexdump' [-Wmissing-prototypes]
217 | void kunit_assert_hexdump(struct string_stream *stream,
| ^
lib/kunit/assert.c:217:1: note: declare 'static' if the function is not
intended to be used outside of this translation unit
217 | void kunit_assert_hexdump(struct string_stream *stream,
| ^
| static
4 warnings generated.
vim +/kunit_assert_print_msg +35 lib/kunit/assert.c
33
34 VISIBLE_IF_KUNIT
> 35 void kunit_assert_print_msg(const struct va_format *message,
36 struct string_stream *stream)
37 {
38 if (message->fmt)
39 string_stream_add(stream, "\n%pV", message);
40 }
41 EXPORT_SYMBOL_IF_KUNIT(kunit_assert_print_msg);
42
43 void kunit_fail_assert_format(const struct kunit_assert *assert,
44const struct va_format *message,
45struct string_stream *stream)
46 {
47 string_stream_add(stream, "%pV", message);
48 }
49 EXPORT_SYMBOL_GPL(kunit_fail_assert_format);
50
51 void kunit_unary_assert_format(const struct kunit_assert *assert,
52 const struct va_format *message,
53 struct string_stream *stream)
54 {
55 struct kunit_unary_assert *unary_assert;
56
57 unary_assert = container_of(assert, struct kunit_unary_assert,
assert);
58
59 if (unary_assert->expected_true)
60 string_stream_add(stream,
61KUNIT_SUBTEST_INDENT "Expected %s to
be true, but is false\n",
62unary_assert->
Re: [PATCH v2] kunit: Cover 'assert.c' with tests
Hi Ivan, kernel test robot noticed the following build errors: [auto build test ERROR on shuah-kselftest/kunit] [also build test ERROR on shuah-kselftest/kunit-fixes linus/master v6.9-rc7 next-20240508] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/kunit-Cover-assert-c-with-tests/20240508-212654 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit patch link: https://lore.kernel.org/r/20240508132557.599213-1-ivan.orlov0322%40gmail.com patch subject: [PATCH v2] kunit: Cover 'assert.c' with tests config: i386-buildonly-randconfig-003-20240509 (https://download.01.org/0day-ci/archive/20240509/202405091439.ed9d3azg-...@intel.com/config) compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240509/202405091439.ed9d3azg-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202405091439.ed9d3azg-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in fs/unicode/utf8-selftest.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/isofs/isofs.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/hfs/hfs.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/sysv/sysv.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/hpfs/hpfs.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/efs/efs.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/qnx6/qnx6.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/adfs/adfs.o WARNING: modpost: missing MODULE_DESCRIPTION() in fs/bcachefs/mean_and_variance_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in crypto/xor.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/kunit.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/kunit-test.o ERROR: modpost: missing MODULE_LICENSE() in lib/kunit/assert_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/assert_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/kunit-example-test.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/zlib_deflate/zlib_deflate.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pinctrl/pinctrl-mcp23s08_i2c.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pinctrl/pinctrl-mcp23s08.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpio/gpio-gw-pld.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpio/gpio-pcf857x.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/console/mdacon.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/clk_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/clk-fractional-divider_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/regulator/da9121-regulator.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/regulator/rt4831-regulator.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/regulator/tps6286x-regulator.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/tty/serial/8250/serial_cs.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/tty/goldfish.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/dtlk.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/tlclk.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-kunit.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-i2c.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-ram.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-raw-ram.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/block/floppy.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/misc/open-dice.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/mfd/arizona.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/mfd/rt4831.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/mfd/qcom-pm8008.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/scsi/aha1542.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/scsi/g_NCR5380.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cdrom/cdrom.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/i82365.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/misc/ezusb.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/misc/isight_firmware.o WARNING: modpost: missing MODULE_DESCRIPTION() in
Re: [PATCH v2] kunit: Cover 'assert.c' with tests
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/kunit]
[also build test WARNING on shuah-kselftest/kunit-fixes linus/master v6.9-rc7
next-20240508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/kunit-Cover-assert-c-with-tests/20240508-212654
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit
patch link:
https://lore.kernel.org/r/20240508132557.599213-1-ivan.orlov0322%40gmail.com
patch subject: [PATCH v2] kunit: Cover 'assert.c' with tests
config: i386-randconfig-004-20240509
(https://download.01.org/0day-ci/archive/20240509/202405091540.xkfmdsal-...@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240509/202405091540.xkfmdsal-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202405091540.xkfmdsal-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/kunit/assert.c:35:6: warning: no previous prototype for
>> 'kunit_assert_print_msg' [-Wmissing-prototypes]
35 | void kunit_assert_print_msg(const struct va_format *message,
| ^~
>> lib/kunit/assert.c:95:23: warning: no previous prototype for 'is_literal'
>> [-Wmissing-prototypes]
95 | VISIBLE_IF_KUNIT bool is_literal(const char *text, long long value)
| ^~
>> lib/kunit/assert.c:173:23: warning: no previous prototype for
>> 'is_str_literal' [-Wmissing-prototypes]
173 | VISIBLE_IF_KUNIT bool is_str_literal(const char *text, const char
*value)
| ^~
>> lib/kunit/assert.c:217:6: warning: no previous prototype for
>> 'kunit_assert_hexdump' [-Wmissing-prototypes]
217 | void kunit_assert_hexdump(struct string_stream *stream,
| ^~~~
vim +/kunit_assert_print_msg +35 lib/kunit/assert.c
33
34 VISIBLE_IF_KUNIT
> 35 void kunit_assert_print_msg(const struct va_format *message,
36 struct string_stream *stream)
37 {
38 if (message->fmt)
39 string_stream_add(stream, "\n%pV", message);
40 }
41 EXPORT_SYMBOL_IF_KUNIT(kunit_assert_print_msg);
42
43 void kunit_fail_assert_format(const struct kunit_assert *assert,
44const struct va_format *message,
45struct string_stream *stream)
46 {
47 string_stream_add(stream, "%pV", message);
48 }
49 EXPORT_SYMBOL_GPL(kunit_fail_assert_format);
50
51 void kunit_unary_assert_format(const struct kunit_assert *assert,
52 const struct va_format *message,
53 struct string_stream *stream)
54 {
55 struct kunit_unary_assert *unary_assert;
56
57 unary_assert = container_of(assert, struct kunit_unary_assert,
assert);
58
59 if (unary_assert->expected_true)
60 string_stream_add(stream,
61KUNIT_SUBTEST_INDENT "Expected %s to
be true, but is false\n",
62unary_assert->condition);
63 else
64 string_stream_add(stream,
65KUNIT_SUBTEST_INDENT "Expected %s to
be false, but is true\n",
66unary_assert->condition);
67 kunit_assert_print_msg(message, stream);
68 }
69 EXPORT_SYMBOL_GPL(kunit_unary_assert_format);
70
71 void kunit_ptr_not_err_assert_format(const struct kunit_assert *assert,
72 const struct va_format *message,
73 struct string_stream *stream)
74 {
75 struct kunit_ptr_not_err_assert *ptr_assert;
76
77 ptr_assert = container_of(assert, struct
kunit_ptr_not_err_assert,
78assert);
79
80 if (!ptr_assert->value) {
81 string_stream_add(stream,
82KUNIT_SUBTEST_INDENT "Expected %s is
not null, but is\n",
83ptr_assert->text);
Re: [PATCH bpf-next 4/4] selftests/bpf: Add post_connect_cb callback
Hi Geliang,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Geliang-Tang/selftests-bpf-Use-post_socket_cb-in-connect_to_fd_opts/20240511-111755
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/2da67a207bfd53057db219e13bd68a7ee82d5d30.1715396405.git.tanggeliang%40kylinos.cn
patch subject: [PATCH bpf-next 4/4] selftests/bpf: Add post_connect_cb callback
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
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
| Closes: https://lore.kernel.org/r/202405141220.s3qjczc4-...@intel.com/
All errors (new ones prefixed by >>):
>> tools/testing/selftests/bpf/prog_tests/bpf_tcp_ca.c:500:26: error: too many
>> arguments to function call, expected single argument 'opts', have 2 arguments
500 | do_test("bpf_cc_cubic", NULL);
| ~~~ ^~~~
lib/clang/18/include/__stddef_null.h:26:14: note: expanded from macro 'NULL'
26 | #define NULL ((void*)0)
| ^~
tools/testing/selftests/bpf/prog_tests/bpf_tcp_ca.c:37:13: note: 'do_test'
declared here
37 | static void do_test(const struct network_helper_opts *opts)
| ^ ~~
1 error generated.
vim +/opts +500 tools/testing/selftests/bpf/prog_tests/bpf_tcp_ca.c
5da7fb04902b0f Martin KaFai Lau 2024-03-22 484
96c3490d6423b7 Miao Xu 2024-05-01 485 static void test_cc_cubic(void)
96c3490d6423b7 Miao Xu 2024-05-01 486 {
96c3490d6423b7 Miao Xu 2024-05-01 487 struct bpf_cc_cubic
*cc_cubic_skel;
96c3490d6423b7 Miao Xu 2024-05-01 488 struct bpf_link *link;
96c3490d6423b7 Miao Xu 2024-05-01 489
96c3490d6423b7 Miao Xu 2024-05-01 490 cc_cubic_skel =
bpf_cc_cubic__open_and_load();
96c3490d6423b7 Miao Xu 2024-05-01 491 if
(!ASSERT_OK_PTR(cc_cubic_skel, "bpf_cc_cubic__open_and_load"))
96c3490d6423b7 Miao Xu 2024-05-01 492 return;
96c3490d6423b7 Miao Xu 2024-05-01 493
96c3490d6423b7 Miao Xu 2024-05-01 494 link =
bpf_map__attach_struct_ops(cc_cubic_skel->maps.cc_cubic);
96c3490d6423b7 Miao Xu 2024-05-01 495 if
(!ASSERT_OK_PTR(link, "bpf_map__attach_struct_ops")) {
96c3490d6423b7 Miao Xu 2024-05-01 496
bpf_cc_cubic__destroy(cc_cubic_skel);
96c3490d6423b7 Miao Xu 2024-05-01 497 return;
96c3490d6423b7 Miao Xu 2024-05-01 498 }
96c3490d6423b7 Miao Xu 2024-05-01 499
96c3490d6423b7 Miao Xu 2024-05-01 @500 do_test("bpf_cc_cubic",
NULL);
96c3490d6423b7 Miao Xu 2024-05-01 501
96c3490d6423b7 Miao Xu 2024-05-01 502 bpf_link__destroy(link);
96c3490d6423b7 Miao Xu 2024-05-01 503
bpf_cc_cubic__destroy(cc_cubic_skel);
96c3490d6423b7 Miao Xu 2024-05-01 504 }
96c3490d6423b7 Miao Xu 2024-05-01 505
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [kunit] 3a35c13007: kunit.VCAP_API_DebugFS_Testsuite.vcap_api_show_admin_raw_test.fail
Hello,
this was reported in
https://lore.kernel.org/all/202404151340.5b152d96-...@intel.com/
since we still observed same failure after the commit is merged in mainline,
we just report again FYI.
kernel test robot noticed
"kunit.VCAP_API_DebugFS_Testsuite.vcap_api_show_admin_raw_test.fail" on:
commit: 3a35c13007dea132a65f07de05c26b87837fadc2 ("kunit: Handle test faults")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed in linus/master 6e51b4b5bbc07e52b226017936874715629932d1]
[test failed on linux-next/master 632483ea8004edfadd035de36e1ab2c7c4f53158]
in testcase: kunit
version:
with following parameters:
group: group-03
compiler: gcc-13
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy
Bridge) with 8G 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
| Closes:
https://lore.kernel.org/oe-lkp/202405241710.148db8b0-oliver.s...@intel.com
[ 116.216583] # vcap_api_show_admin_raw_test: EXPECTATION FAILED at
drivers/net/ethernet/microchip/vcap/vcap_api_debugfs_kunit.c:377
Expected test_expected == test_pr_buffer[0], but
test_expected == " addr: 786, X6 rule, keysets:
VCAP_KFS_MAC_ETYPE
"
test_pr_buffer[0] == ""
[ 116.222467] not ok 2 vcap_api_show_admin_raw_test
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240524/202405241710.148db8b0-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH HID 03/13] HID: bpf: implement HID-BPF through bpf_struct_ops
Hi Benjamin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 70ec81c2e2b4005465ad0d042e90b36087c36104]
url:
https://github.com/intel-lab-lkp/linux/commits/Benjamin-Tissoires/HID-rename-struct-hid_bpf_ops-into-hid_ops/20240528-21
base: 70ec81c2e2b4005465ad0d042e90b36087c36104
patch link:
https://lore.kernel.org/r/20240528-hid_bpf_struct_ops-v1-3-8c6663df27d8%40kernel.org
patch subject: [PATCH HID 03/13] HID: bpf: implement HID-BPF through
bpf_struct_ops
config: i386-buildonly-randconfig-002-20240531
(https://download.01.org/0day-ci/archive/20240531/202405312035.u1rzn04z-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240531/202405312035.u1rzn04z-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202405312035.u1rzn04z-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/bpf_verifier.h:7:0,
from drivers/hid/bpf/hid_bpf_struct_ops.c:10:
drivers/hid/bpf/hid_bpf_struct_ops.c: In function 'hid_bpf_struct_ops_init':
>> include/linux/bpf.h:1844:50: warning: statement with no effect
>> [-Wunused-value]
#define register_bpf_struct_ops(st_ops, type) ({ (void *)(st_ops); 0; })
^~~~
drivers/hid/bpf/hid_bpf_struct_ops.c:244:9: note: in expansion of macro
'register_bpf_struct_ops'
return register_bpf_struct_ops(&bpf_hid_bpf_ops, hid_bpf_ops);
^~~
vim +1844 include/linux/bpf.h
c196906d50e360d Hou Tao 2021-10-25 1834
c196906d50e360d Hou Tao 2021-10-25 1835 int
bpf_struct_ops_test_run(struct bpf_prog *prog, const union bpf_attr *kattr,
c196906d50e360d Hou Tao 2021-10-25 1836
union bpf_attr __user *uattr);
c196906d50e360d Hou Tao 2021-10-25 1837 #endif
f6be98d19985411 Kui-Feng Lee 2024-01-19 1838 int
bpf_struct_ops_desc_init(struct bpf_struct_ops_desc *st_ops_desc,
f6be98d19985411 Kui-Feng Lee 2024-01-19 1839
struct btf *btf,
f6be98d19985411 Kui-Feng Lee 2024-01-19 1840
struct bpf_verifier_log *log);
1338b93346587a2 Kui-Feng Lee 2024-01-19 1841 void
bpf_map_struct_ops_info_fill(struct bpf_map_info *info, struct bpf_map *map);
1611603537a4b88 Kui-Feng Lee 2024-02-08 1842 void
bpf_struct_ops_desc_release(struct bpf_struct_ops_desc *st_ops_desc);
27ae7997a66174c Martin KaFai Lau 2020-01-08 1843 #else
f6be98d19985411 Kui-Feng Lee 2024-01-19 @1844 #define
register_bpf_struct_ops(st_ops, type) ({ (void *)(st_ops); 0; })
85d33df357b6346 Martin KaFai Lau 2020-01-08 1845 static inline bool
bpf_try_module_get(const void *data, struct module *owner)
85d33df357b6346 Martin KaFai Lau 2020-01-08 1846 {
85d33df357b6346 Martin KaFai Lau 2020-01-08 1847 return
try_module_get(owner);
85d33df357b6346 Martin KaFai Lau 2020-01-08 1848 }
85d33df357b6346 Martin KaFai Lau 2020-01-08 1849 static inline void
bpf_module_put(const void *data, struct module *owner)
85d33df357b6346 Martin KaFai Lau 2020-01-08 1850 {
85d33df357b6346 Martin KaFai Lau 2020-01-08 1851 module_put(owner);
85d33df357b6346 Martin KaFai Lau 2020-01-08 1852 }
85d33df357b6346 Martin KaFai Lau 2020-01-08 1853 static inline int
bpf_struct_ops_map_sys_lookup_elem(struct bpf_map *map,
85d33df357b6346 Martin KaFai Lau 2020-01-08 1854
void *key,
85d33df357b6346 Martin KaFai Lau 2020-01-08 1855
void *value)
85d33df357b6346 Martin KaFai Lau 2020-01-08 1856 {
85d33df357b6346 Martin KaFai Lau 2020-01-08 1857 return -EINVAL;
85d33df357b6346 Martin KaFai Lau 2020-01-08 1858 }
68b04864ca425d1 Kui-Feng Lee 2023-03-22 1859 static inline int
bpf_struct_ops_link_create(union bpf_attr *attr)
68b04864ca425d1 Kui-Feng Lee 2023-03-22 1860 {
68b04864ca425d1 Kui-Feng Lee 2023-03-22 1861 return -EOPNOTSUPP;
68b04864ca425d1 Kui-Feng Lee 2023-03-22 1862 }
1338b93346587a2 Kui-Feng Lee 2024-01-19 1863 static inline void
bpf_map_struct_ops_info_fill(struct bpf_map_info *info, struct bpf_map *map)
1338b93346587a2 Kui-Feng Lee 2024-01-19 1864 {
1338b93346587a2 Kui-Feng Lee 2024-01-19 1865 }
68b04864ca425d1 Kui-Feng Lee 2023-03-22 1866
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 3/4] ALSA: timer: Introduce virtual userspace-driven timers
Hi Ivan, kernel test robot noticed the following build errors: [auto build test ERROR on tiwai-sound/for-next] [also build test ERROR on tiwai-sound/for-linus linus/master v6.11-rc2 next-20240808] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Orlov/ALSA-aloop-Allow-using-global-timers/20240806-210332 base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next patch link: https://lore.kernel.org/r/20240806125243.449959-4-ivan.orlov0322%40gmail.com patch subject: [PATCH v3 3/4] ALSA: timer: Introduce virtual userspace-driven timers config: arm-randconfig-r064-20240807 (https://download.01.org/0day-ci/archive/20240808/202408081612.hvfwzvlb-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240808/202408081612.hvfwzvlb-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202408081612.hvfwzvlb-...@intel.com/ All errors (new ones prefixed by >>): arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_submit_wmt_recv_urb': drivers/bluetooth/btmtk.c:531:(.text+0x6c2): undefined reference to `usb_alloc_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:537:(.text+0x6e6): undefined reference to `usb_free_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:561:(.text+0x750): undefined reference to `usb_anchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:562:(.text+0x75a): undefined reference to `usb_submit_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:567:(.text+0x796): undefined reference to `usb_unanchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:570:(.text+0x7a0): undefined reference to `usb_free_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_submit_intr_urb': drivers/bluetooth/btmtk.c:1174:(.text+0x80e): undefined reference to `usb_alloc_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1181:(.text+0x83a): undefined reference to `usb_free_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1195:(.text+0x8c4): undefined reference to `usb_anchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1197:(.text+0x8cc): undefined reference to `usb_submit_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1202:(.text+0x908): undefined reference to `usb_unanchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1205:(.text+0x912): undefined reference to `usb_free_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_suspend': drivers/bluetooth/btmtk.c:1265:(.text+0x988): undefined reference to `usb_kill_anchored_urbs' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_intr_complete': drivers/bluetooth/btmtk.c:1145:(.text+0xbf2): undefined reference to `usb_anchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1147:(.text+0xbfc): undefined reference to `usb_submit_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:1157:(.text+0xc48): undefined reference to `usb_unanchor_urb' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `__set_mtk_intr_interface': drivers/bluetooth/btmtk.c:991:(.text+0xcf4): undefined reference to `usb_set_interface' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_isointf_init': drivers/bluetooth/btmtk.c:1224:(.text+0xd30): undefined reference to `usb_kill_anchored_urbs' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_hci_wmt_sync': drivers/bluetooth/btmtk.c:610:(.text+0xf26): undefined reference to `usb_autopm_get_interface' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:618:(.text+0xf54): undefined reference to `usb_autopm_put_interface' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.c:625:(.text+0xf7e): undefined reference to `usb_autopm_put_interface' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_reg_read': drivers/bluetooth/btmtk.c:790:(.text+0x1248): undefined reference to `usb_control_msg' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_uhw_reg_write': drivers/bluetooth/btmtk.c:738:(.text+0x12e0): undefined reference to `usb_control_msg' arm-linux-gnueabi-ld: drivers/bluetooth/btmtk.o: in function `btmtk_usb_uhw_reg_read': drivers/bluetooth/btmtk.c:761:(.text+0x1374): undefined reference to `usb_control_msg' arm
Re: [PATCH v2 3/3] iommufd/selftest: Add coverage for reserved IOVAs
Hi Nicolin, kernel test robot noticed the following build errors: [auto build test ERROR on shuah-kselftest/next] [also build test ERROR on shuah-kselftest/fixes linus/master v6.11-rc2 next-20240809] [cannot apply to joro-iommu/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Nicolin-Chen/iommufd-Reorder-include-files/20240803-210818 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/544ab894a301c83eb9f9d7a6326f4cb87f517019.1722644866.git.nicolinc%40nvidia.com patch subject: [PATCH v2 3/3] iommufd/selftest: Add coverage for reserved IOVAs config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20240809/202408092301.m51npxgl-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240809/202408092301.m51npxgl-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202408092301.m51npxgl-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/usb_debug.o >> ERROR: modpost: "iommu_dma_prepare_msi" [drivers/iommu/iommufd/iommufd.ko] >> undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] lib/math: Add int_pow test suite
Hi Luis,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc4]
[also build test WARNING on linus/master next-20240819]
[cannot apply to akpm-mm/mm-nonmm-unstable]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_pow-test-suite/20240819-094252
base: v6.11-rc4
patch link:
https://lore.kernel.org/r/20240819014115.221135-1-luis.hernandez093%40gmail.com
patch subject: [PATCH v2] lib/math: Add int_pow test suite
config: i386-buildonly-randconfig-004-20240819
(https://download.01.org/0day-ci/archive/20240819/202408191754.to9uud0n-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240819/202408191754.to9uud0n-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202408191754.to9uud0n-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/math/tests/int_pow_kunit.c:22:11: warning: integer literal is too large
>> to be represented in a signed integer type, interpreting as unsigned
>> [-Wimplicitly-unsigned-literal]
22 | { 2, 63, 9223372036854775808, "Large result"},
| ^
1 warning generated.
vim +22 lib/math/tests/int_pow_kunit.c
12
13 static const struct test_case_params params[] = {
14 { 64, 0, 1, "Power of zero" },
15 { 64, 1, 64, "Power of one"},
16 { 0, 5, 0, "Base zero" },
17 { 1, 64, 1, "Base one" },
18 { 2, 2, 4, "Two squared"},
19 { 2, 3, 8, "Two cubed"},
20 { 5, 5, 3125, "Five raised to the fith power" },
21 { U64_MAX, 1, U64_MAX, "Max base" },
> 22 { 2, 63, 9223372036854775808, "Large result"},
23 };
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] lib/math: Add int_pow test suite
Hi Luis,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc4]
[also build test WARNING on linus/master next-20240819]
[cannot apply to akpm-mm/mm-nonmm-unstable]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_pow-test-suite/20240819-094252
base: v6.11-rc4
patch link:
https://lore.kernel.org/r/20240819014115.221135-1-luis.hernandez093%40gmail.com
patch subject: [PATCH v2] lib/math: Add int_pow test suite
config: sh-allmodconfig
(https://download.01.org/0day-ci/archive/20240819/202408191958.xq9sr93k-...@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240819/202408191958.xq9sr93k-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202408191958.xq9sr93k-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/math/tests/int_pow_kunit.c:22:18: warning: integer constant is so large
>> that it is unsigned
22 | { 2, 63, 9223372036854775808, "Large result"},
| ^~~
vim +22 lib/math/tests/int_pow_kunit.c
12
13 static const struct test_case_params params[] = {
14 { 64, 0, 1, "Power of zero" },
15 { 64, 1, 64, "Power of one"},
16 { 0, 5, 0, "Base zero" },
17 { 1, 64, 1, "Base one" },
18 { 2, 2, 4, "Two squared"},
19 { 2, 3, 8, "Two cubed"},
20 { 5, 5, 3125, "Five raised to the fith power" },
21 { U64_MAX, 1, U64_MAX, "Max base" },
> 22 { 2, 63, 9223372036854775808, "Large result"},
23 };
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] selftests: fix relative rpath usage
Hi Eugene, kernel test robot noticed the following build warnings: [auto build test WARNING on shuah-kselftest/next] [also build test WARNING on shuah-kselftest/fixes tiwai-sound/for-next tiwai-sound/for-linus bpf-next/master bpf/master linus/master v6.11-rc3 next-20240816] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Eugene-Syromiatnikov/selftests-fix-relative-rpath-usage/20240814-091042 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/20240812165650.GA5102%40asgard.redhat.com patch subject: [PATCH v2] selftests: fix relative rpath usage :: branch date: 5 days ago :: commit date: 5 days ago compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240819/202408190453.wshnzqqj-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/r/202408190453.wshnzqqj-...@intel.com/ All warnings (new ones prefixed by >>): >> clang: warning: -Wl,-rpath=$ORIGIN/: 'linker' input unused >> [-Wunused-command-line-argument] >> clang: warning: argument unused during compilation: '-Lkselftest/kvm' >> [-Wunused-command-line-argument] -- >> clang: warning: -Wl,-rpath=$ORIGIN/: 'linker' input unused >> [-Wunused-command-line-argument] >> clang: warning: argument unused during compilation: '-Lkselftest/net/tcp_ao' >> [-Wunused-command-line-argument] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] selftests: fix relative rpath usage
Hello,
kernel test robot noticed "segfault_at_ip_sp_error" on:
commit: 782e28421b3410522d5b50feb30e8fa10da44492 ("[PATCH v2] selftests: fix
relative rpath usage")
url:
https://github.com/intel-lab-lkp/linux/commits/Eugene-Syromiatnikov/selftests-fix-relative-rpath-usage/20240814-091042
base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git
next
patch link: https://lore.kernel.org/all/20240812165650.ga5...@asgard.redhat.com/
patch subject: [PATCH v2] selftests: fix relative rpath usage
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: group-01
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)
besides, we also noticed some tests failed on this change:
8afc0816f5f6213c 782e28421b3410522d5b50feb30
---
fail:runs %reproductionfail:runs
| | |
:4 100% 4:4 dmesg.segfault_at_ip_sp_error
:4 100% 4:4
kernel-selftests.exec.load_address.static.0x1000.fail
:4 100% 4:4
kernel-selftests.exec.load_address.static.0x100.fail
:4 100% 4:4
kernel-selftests.exec.load_address.static.0x20.fail
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
| Closes:
https://lore.kernel.org/oe-lkp/202408251749.7e390194-oliver.s...@intel.com
user :notice: [ 458.511077] 2024-08-23 12:25:42 make -j36 -C dt
user :notice: [ 458.527252] make: Entering directory
'/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-782e28421b3410522d5b50feb30e8fa10da44492/tools/testing/selftests/dt'
kern :info : [ 460.458153] load_address.st[7491]: segfault at 28 ip
7f1137a2b5e6 sp 7ffddc0fd6d0 error 4 in
load_address.static.0x1000[d5e6,7f1137a27000+7a000] likely on CPU 2 (core 2,
socket 0)
kern :info : [ 460.459808] Code: 53 48 81 ec d8 00 00 00 48 89 b5 68 ff ff ff
48 89 95 38 ff ff ff 89 8d 54 ff ff ff 4c 89 85 48 ff ff ff 44 89 8d 50 ff ff
ff <64> 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 48 c7 85 70 ff ff ff
All code
0: 53 push %rbx
1: 48 81 ec d8 00 00 00sub$0xd8,%rsp
8: 48 89 b5 68 ff ff ffmov%rsi,-0x98(%rbp)
f: 48 89 95 38 ff ff ffmov%rdx,-0xc8(%rbp)
16: 89 8d 54 ff ff ff mov%ecx,-0xac(%rbp)
1c: 4c 89 85 48 ff ff ffmov%r8,-0xb8(%rbp)
23: 44 89 8d 50 ff ff ffmov%r9d,-0xb0(%rbp)
2a:* 64 48 8b 04 25 28 00mov%fs:0x28,%rax<-- trapping
instruction
31: 00 00
33: 48 89 45 c8 mov%rax,-0x38(%rbp)
37: 31 c0 xor%eax,%eax
39: 48 rex.W
3a: c7 .byte 0xc7
3b: 85 70 fftest %esi,-0x1(%rax)
3e: ff (bad)
3f: ff .byte 0xff
Code starting with the faulting instruction
===
0: 64 48 8b 04 25 28 00mov%fs:0x28,%rax
7: 00 00
9: 48 89 45 c8 mov%rax,-0x38(%rbp)
d: 31 c0 xor%eax,%eax
f: 48 rex.W
10: c7 .byte 0xc7
11: 85 70 fftest %esi,-0x1(%rax)
14: ff (bad)
15: ff .byte 0xff
kern :info : [ 460.571500] load_address.st[7510]: segfault at 28 ip
7fa9ec0045e6 sp 7ffd3ba861b0 error 4 in
load_address.static.0x20[2045e6,7fa9ec00+7a000] likely on CPU 2 (core
2, socket 0)
kern :info : [ 460.573155] Code: 53 48 81 ec d8 00 00 00 48 89 b5 68 ff ff ff
48 89 95 38 ff ff ff 89 8d 54 ff ff ff 4c 89 85 48 ff ff ff 44 89 8d 50 ff ff
ff <64> 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 48 c7 85 70 ff ff ff
All code
0: 53 push %rbx
1: 48 81 ec d8 00 00 00sub$0xd8,%rsp
8: 48 89 b5 68 ff ff ffmov%rsi,-0x98(%rbp)
f: 48 89 95 38 ff ff ffmov%rdx,-0xc8(%rbp)
16: 89 8d 54 ff ff ff mov%ecx,-0xac(%rbp)
1c: 4c 89 85 48 ff ff ffmov%r8,-0xb8(%rbp)
23: 44 89 8d 50 ff ff ffmov%r9d,-0xb0(%rbp)
2a:* 64 48 8b 04 25 28 00mov%fs:0x28,%rax<-- trapping
instruction
31: 00 00
33: 48 89 45 c8 mov%rax,-0x38(%rbp)
37: 31 c0 xor%eax,%eax
39: 48 rex.W
3a: c7 .byte 0xc7
3b: 85 70 fftest %esi,-0x1(%rax)
3e: ff (bad)
3f: ff
Re: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
Hi Christophe,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes shuah-kselftest/next
shuah-kselftest/fixes crng-random/master linus/master v6.11-rc5 next-20240823]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Christophe-Leroy/asm-generic-unaligned-h-Extract-common-header-for-vDSO/20240826-103525
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link:
https://lore.kernel.org/r/315e3a268b165b6edad7dcb723b0d8a506a56c4e.1724309198.git.christophe.leroy%40csgroup.eu
patch subject: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
config: x86_64-buildonly-randconfig-002-20240826
(https://download.01.org/0day-ci/archive/20240826/202408261757.d4goewe9-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240826/202408261757.d4goewe9-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202408261757.d4goewe9-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/trace/events/page_ref.h:11,
from mm/debug_page_ref.c:6:
>> include/trace/events/mmflags.h:168:5: warning: "VM_DROPPABLE" is not
>> defined, evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^~~~
>> include/trace/events/mmflags.h:168:21: warning: "VM_NONE" is not defined,
>> evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^~~
In file included from include/trace/events/page_ref.h:11,
from include/trace/define_trace.h:95,
from include/trace/events/page_ref.h:135:
>> include/trace/events/mmflags.h:168:5: warning: "VM_DROPPABLE" is not
>> defined, evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^~~~
>> include/trace/events/mmflags.h:168:21: warning: "VM_NONE" is not defined,
>> evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^~~
In file included from include/trace/events/page_ref.h:11,
from include/trace/trace_events.h:94,
from include/trace/define_trace.h:102:
>> include/trace/events/mmflags.h:169: warning: "IF_HAVE_VM_DROPPABLE" redefined
169 | # define IF_HAVE_VM_DROPPABLE(flag, name) {flag, name},
|
include/trace/events/mmflags.h:171: note: this is the location of the
previous definition
171 | # define IF_HAVE_VM_DROPPABLE(flag, name)
|
vim +/VM_DROPPABLE +168 include/trace/events/mmflags.h
167
> 168 #if VM_DROPPABLE != VM_NONE
> 169 # define IF_HAVE_VM_DROPPABLE(flag, name) {flag, name},
170 #else
171 # define IF_HAVE_VM_DROPPABLE(flag, name)
172 #endif
173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
Hi Christophe,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes shuah-kselftest/next
shuah-kselftest/fixes linus/master v6.11-rc5 next-20240823]
[cannot apply to crng-random/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Christophe-Leroy/asm-generic-unaligned-h-Extract-common-header-for-vDSO/20240826-103525
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link:
https://lore.kernel.org/r/315e3a268b165b6edad7dcb723b0d8a506a56c4e.1724309198.git.christophe.leroy%40csgroup.eu
patch subject: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240826/202408261734.uavnh7mv-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240826/202408261734.uavnh7mv-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202408261734.uavnh7mv-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from mm/debug_page_ref.c:6:
In file included from include/trace/events/page_ref.h:11:
include/trace/events/mmflags.h:168:5: warning: 'VM_DROPPABLE' is not
defined, evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^
include/trace/events/mmflags.h:168:21: warning: 'VM_NONE' is not defined,
evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^
In file included from mm/debug_page_ref.c:6:
In file included from include/trace/events/page_ref.h:135:
In file included from include/trace/define_trace.h:95:
In file included from include/trace/events/page_ref.h:11:
include/trace/events/mmflags.h:168:5: warning: 'VM_DROPPABLE' is not
defined, evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^
include/trace/events/mmflags.h:168:21: warning: 'VM_NONE' is not defined,
evaluates to 0 [-Wundef]
168 | #if VM_DROPPABLE != VM_NONE
| ^
In file included from mm/debug_page_ref.c:6:
In file included from include/trace/events/page_ref.h:135:
In file included from include/trace/define_trace.h:102:
In file included from include/trace/trace_events.h:94:
In file included from include/trace/events/page_ref.h:11:
>> include/trace/events/mmflags.h:169:10: warning: 'IF_HAVE_VM_DROPPABLE' macro
>> redefined [-Wmacro-redefined]
169 | # define IF_HAVE_VM_DROPPABLE(flag, name) {flag, name},
| ^
include/trace/events/mmflags.h:171:10: note: previous definition is here
171 | # define IF_HAVE_VM_DROPPABLE(flag, name)
| ^
5 warnings generated.
vim +/IF_HAVE_VM_DROPPABLE +169 include/trace/events/mmflags.h
7677f7fd8be766 Axel Rasmussen 2021-05-04 167
41e2c674b334ed Christophe Leroy 2024-08-22 @168 #if VM_DROPPABLE != VM_NONE
9651fcedf7b92d Jason A. Donenfeld 2022-12-08 @169 # define
IF_HAVE_VM_DROPPABLE(flag, name) {flag, name},
9651fcedf7b92d Jason A. Donenfeld 2022-12-08 170 #else
9651fcedf7b92d Jason A. Donenfeld 2022-12-08 171 # define
IF_HAVE_VM_DROPPABLE(flag, name)
9651fcedf7b92d Jason A. Donenfeld 2022-12-08 172 #endif
9651fcedf7b92d Jason A. Donenfeld 2022-12-08 173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
Hi Christophe,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes shuah-kselftest/next
shuah-kselftest/fixes linus/master v6.11-rc5 next-20240826]
[cannot apply to crng-random/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Christophe-Leroy/asm-generic-unaligned-h-Extract-common-header-for-vDSO/20240826-103525
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link:
https://lore.kernel.org/r/315e3a268b165b6edad7dcb723b0d8a506a56c4e.1724309198.git.christophe.leroy%40csgroup.eu
patch subject: [PATCH v2 07/17] mm: Define VM_DROPPABLE for powerpc/32
config: um-randconfig-r122-20240826
(https://download.01.org/0day-ci/archive/20240827/202408270553.2s5d14ar-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240827/202408270553.2s5d14ar-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202408270553.2s5d14ar-...@intel.com/
sparse warnings: (new ones prefixed by >>)
mm/debug_page_ref.c: note: in included file (through
include/trace/events/page_ref.h):
>> include/trace/events/mmflags.h:168:5: sparse: sparse: undefined preprocessor
>> identifier 'VM_DROPPABLE'
>> include/trace/events/mmflags.h:168:21: sparse: sparse: undefined
>> preprocessor identifier 'VM_NONE'
mm/debug_page_ref.c: note: in included file (through
include/trace/events/page_ref.h, include/trace/define_trace.h,
include/trace/events/page_ref.h):
>> include/trace/events/mmflags.h:168:5: sparse: sparse: undefined preprocessor
>> identifier 'VM_DROPPABLE'
>> include/trace/events/mmflags.h:168:21: sparse: sparse: undefined
>> preprocessor identifier 'VM_NONE'
mm/debug_page_ref.c: note: in included file (through
include/trace/events/page_ref.h, include/trace/trace_events.h,
include/trace/define_trace.h, ...):
include/trace/events/mmflags.h:169:10: sparse: sparse: preprocessor token
IF_HAVE_VM_DROPPABLE redefined
mm/debug_page_ref.c: note: in included file (through
include/trace/events/page_ref.h):
include/trace/events/mmflags.h:171:10: sparse: this was the original
definition
vim +/VM_DROPPABLE +168 include/trace/events/mmflags.h
167
> 168 #if VM_DROPPABLE != VM_NONE
169 # define IF_HAVE_VM_DROPPABLE(flag, name) {flag, name},
170 #else
171 # define IF_HAVE_VM_DROPPABLE(flag, name)
172 #endif
173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1] selftests:tdx:Use min macro
Hi Yan,
kernel test robot noticed the following build errors:
[auto build test ERROR on shuah-kselftest/next]
[also build test ERROR on shuah-kselftest/fixes linus/master v6.11-rc5
next-20240826]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Yan-Zhen/selftests-tdx-Use-min-macro/20240822-125041
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:
https://lore.kernel.org/r/20240822044630.1267500-1-yanzhen%40vivo.com
patch subject: [PATCH v1] selftests:tdx:Use min macro
:: branch date: 5 days ago
:: commit date: 5 days ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240827/202408271330.hmq39dwo-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202408271330.hmq39dwo-...@intel.com/
All errors (new ones prefixed by >>):
>> tdx_guest_test.c:121:14: error: call to undeclared function 'min'; ISO C99
>> and later do not support implicit function declarations
>> [-Wimplicit-function-declaration]
121 | line_len = min((len - j), rowsize);
|^
1 error generated.
vim +/min +121 tools/testing/selftests/tdx/tdx_guest_test.c
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 111
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 112 static void
print_array_hex(const char *title, const char *prefix_str,
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 113
const void *buf, int len)
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 114 {
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 115 int i, j,
line_len, rowsize = HEX_DUMP_SIZE;
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 116 const __u8 *ptr
= buf;
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 117
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 118
printf("\t\t%s", title);
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 119
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 120 for (j = 0; j <
len; j += rowsize) {
712bf3fd186eaf Yan Zhen 2024-08-22 @121
line_len = min((len - j), rowsize);
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 122
printf("%s%.8x:", prefix_str, j);
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 123 for (i
= 0; i < line_len; i++)
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 124
printf(" %.2x", ptr[j + i]);
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 125
printf("\n");
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 126 }
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 127
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 128 printf("\n");
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 129 }
00e07cfbdf0b23 Kuppuswamy Sathyanarayanan 2022-11-16 130
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] selftests: vDSO: Do not rely on $ARCH for vdso_test_getrandom && vdso_test_chacha
Hi Christophe, kernel test robot noticed the following build errors: [auto build test ERROR on crng-random/master] [cannot apply to shuah-kselftest/next shuah-kselftest/fixes linus/master v6.11-rc6 next-20240830] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Christophe-Leroy/selftests-vDSO-Do-not-rely-on-ARCH-for-vdso_test_getrandom-vdso_test_chacha/20240901-011346 base: https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git master patch link: https://lore.kernel.org/r/ddf594c81787dba708fc392cb03027470dee64fb.1725124064.git.christophe.leroy%40csgroup.eu patch subject: [PATCH] selftests: vDSO: Do not rely on $ARCH for vdso_test_getrandom && vdso_test_chacha :: branch date: 20 hours ago :: commit date: 20 hours ago compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240901/202409012034.hcmbzcre-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/r/202409012034.hcmbzcre-...@intel.com/ All errors (new ones prefixed by >>): In file included from vdso_test_chacha-asm.S:5: >> ./../../../../arch/x86/entry/vdso/vgetrandom-chacha.S:7:10: fatal error: >> 'asm/frame.h' file not found 7 | #include | ^ 1 error generated. vim +7 tools/testing/selftests/vDSO/./../../../../arch/x86/entry/vdso/vgetrandom-chacha.S 33385150ac456f6 Jason A. Donenfeld 2022-11-18 @7 #include 33385150ac456f6 Jason A. Donenfeld 2022-11-18 8 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] selftests/futex: Create test for robust list
Hi André,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on linus/master v6.11-rc6 next-20240830]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Andr-Almeida/selftests-futex-Create-test-for-robust-list/20240830-023631
base: tip/locking/core
patch link:
https://lore.kernel.org/r/20240829183509.446934-1-andrealmeid%40igalia.com
patch subject: [PATCH] selftests/futex: Create test for robust list
:: branch date: 3 days ago
:: commit date: 3 days ago
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240901/202409012132.wvayz660-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202409012132.wvayz660-...@intel.com/
All error/warnings (new ones prefixed by >>):
robust_list.c: In function 'futex2_wait':
>> robust_list.c:53:24: error: 'SYS_futex_wait' undeclared (first use in this
>> function); did you mean 'SYS_futex_waitv'?
53 | return syscall(SYS_futex_wait, futex, val, ~0U,
FUTEX2_SIZE_U32, timo, CLOCK_MONOTONIC);
|^~
|SYS_futex_waitv
robust_list.c:53:24: note: each undeclared identifier is reported only once
for each function it appears in
>> robust_list.c:54:1: warning: control reaches end of non-void function
>> [-Wreturn-type]
54 | }
| ^
vim +53 tools/testing/selftests/futex/functional/robust_list.c
3306ef10715f1b André Almeida 2024-08-29 50
3306ef10715f1b André Almeida 2024-08-29 51 int futex2_wait(void *futex, int
val, struct timespec *timo)
3306ef10715f1b André Almeida 2024-08-29 52 {
3306ef10715f1b André Almeida 2024-08-29 @53 return syscall(SYS_futex_wait,
futex, val, ~0U, FUTEX2_SIZE_U32, timo, CLOCK_MONOTONIC);
3306ef10715f1b André Almeida 2024-08-29 54 }
3306ef10715f1b André Almeida 2024-08-29 55
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next] wireguard: allowedips: Add WGALLOWEDIP_F_REMOVE_ME flag
Hi Jordan, kernel test robot noticed the following build warnings: [auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Jordan-Rife/wireguard-allowedips-Add-WGALLOWEDIP_F_REMOVE_ME-flag/20240831-034712 base: net-next/main patch link: https://lore.kernel.org/r/20240830194103.2186774-1-jrife%40google.com patch subject: [PATCH net-next] wireguard: allowedips: Add WGALLOWEDIP_F_REMOVE_ME flag config: i386-randconfig-062-20240901 (https://download.01.org/0day-ci/archive/20240901/202409011256.cwrnquxq-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240901/202409011256.cwrnquxq-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409011256.cwrnquxq-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/net/wireguard/allowedips.c:257:24: sparse: sparse: incorrect type in >> argument 1 (different address spaces) @@ expected struct list_head >> *entry @@ got struct list_head [noderef] __rcu * @@ drivers/net/wireguard/allowedips.c:257:24: sparse: expected struct list_head *entry drivers/net/wireguard/allowedips.c:257:24: sparse: got struct list_head [noderef] __rcu * >> drivers/net/wireguard/allowedips.c:258:9: sparse: sparse: cast removes >> address space '__rcu' of expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:269:24: sparse: sparse: cast removes address space '__rcu' of expression drivers/net/wireguard/allowedips.c:270:26: sparse: sparse: cast removes address space '__rcu' of expression >> drivers/net/wireguard/allowedips.c:276:19: sparse: sparse: incorrect type in >> argument 1 (different address spaces) @@ expected struct callback_head >> *head @@ got struct callback_head [noderef] __rcu * @@ drivers/net/wireguard/allowedips.c:276:19: sparse: expected struct callback_head *head drivers/net/wireguard/allowedips.c:276:19: sparse: got struct callback_head [noderef] __rcu * drivers/net/wireguard/allowedips.c:294:18: sparse: sparse: incompatible types in comparison expression (different address spaces): drivers/net/wireguard/allowedips.c:294:18: sparse:struct wg_peer * drivers/net/wireguard/allowedips.c:294:18: sparse:struct wg_peer [noderef] __rcu * >> drivers/net/wireguard/allowedips.c:384:25: sparse: sparse: incorrect type in >> argument 1 (different address spaces) @@ expected struct allowedips_node >> [noderef] __rcu *node @@ got struct allowedips_node *[assigned] node @@ >> drivers/net/wireguard/allowedips.c:258:9: sparse: sparse: dereference of >> noderef expression >> drivers/net/wireguard/allowedips.c:258:9: sparse: sparse: dereference of >> noderef expression drivers/net/wireguard/allowedips.c:259:22: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:259:38: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:261:17: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:264:44: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:265:50: sparse: sparse: dereference of noderef expression drivers/net/wireguard/allowedips.c:268:
Re: [PATCH] selftests/futex: Create test for robust list
Hi André,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on linus/master v6.11-rc5 next-20240830]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Andr-Almeida/selftests-futex-Create-test-for-robust-list/20240830-023631
base: tip/locking/core
patch link:
https://lore.kernel.org/r/20240829183509.446934-1-andrealmeid%40igalia.com
patch subject: [PATCH] selftests/futex: Create test for robust list
:: branch date: 2 days ago
:: commit date: 2 days ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240831/202408311654.me6a2xuf-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202408311654.me6a2xuf-...@intel.com/
All errors (new ones prefixed by >>):
>> robust_list.c:53:17: error: use of undeclared identifier 'SYS_futex_wait';
>> did you mean 'futex_wait'?
53 | return syscall(SYS_futex_wait, futex, val, ~0U,
FUTEX2_SIZE_U32, timo, CLOCK_MONOTONIC);
|^~
|futex_wait
../include/futextest.h:78:1: note: 'futex_wait' declared here
78 | futex_wait(futex_t *uaddr, futex_t val, struct timespec *timeout,
int opflags)
| ^
>> robust_list.c:121:6: error: address argument to atomic operation must be a
>> pointer to _Atomic type ('int *' invalid)
121 | if (atomic_compare_exchange_strong(futex, &zero, tid)) {
| ^ ~
/opt/cross/clang-617a15a9ea/lib/clang/18/include/stdatomic.h:144:67: note:
expanded from macro 'atomic_compare_exchange_strong'
144 | #define atomic_compare_exchange_strong(object, expected, desired)
__c11_atomic_compare_exchange_strong(object, expected, desired,
__ATOMIC_SEQ_CST, __ATOMIC_SEQ_CST)
| ^
~~
robust_list.c:147:9: error: address argument to atomic operation must be a
pointer to _Atomic type ('int *' invalid)
147 | tid = atomic_load(futex);
| ^ ~
/opt/cross/clang-617a15a9ea/lib/clang/18/include/stdatomic.h:138:29: note:
expanded from macro 'atomic_load'
138 | #define atomic_load(object) __c11_atomic_load(object,
__ATOMIC_SEQ_CST)
| ^ ~~
robust_list.c:150:3: error: address argument to atomic operation must be a
pointer to _Atomic type ('int *' invalid)
150 | atomic_store(futex, tid);
| ^~
/opt/cross/clang-617a15a9ea/lib/clang/18/include/stdatomic.h:135:39: note:
expanded from macro 'atomic_store'
135 | #define atomic_store(object, desired) __c11_atomic_store(object,
desired, __ATOMIC_SEQ_CST)
| ^ ~~
4 errors generated.
vim +53 tools/testing/selftests/futex/functional/robust_list.c
3306ef10715f1b André Almeida 2024-08-29 50
3306ef10715f1b André Almeida 2024-08-29 51 int futex2_wait(void *futex, int
val, struct timespec *timo)
3306ef10715f1b André Almeida 2024-08-29 52 {
3306ef10715f1b André Almeida 2024-08-29 @53 return syscall(SYS_futex_wait,
futex, val, ~0U, FUTEX2_SIZE_U32, timo, CLOCK_MONOTONIC);
3306ef10715f1b André Almeida 2024-08-29 54 }
3306ef10715f1b André Almeida 2024-08-29 55
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[crng-random:jd/arm64-vdso] [selftests] f68b079b1d: kernel-selftests.vDSO.vdso_standalone_test_x86.fail
Hello,
kernel test robot noticed "kernel-selftests.vDSO.vdso_standalone_test_x86.fail"
on:
commit: f68b079b1d5ec46687a097347303b616927eb9ff ("selftests: vDSO: build tests
with O2 optimization")
https://git.kernel.org/cgit/linux/kernel/git/crng/random.git jd/arm64-vdso
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: group-03
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
| Closes:
https://lore.kernel.org/oe-lkp/202409082121.553d4c89-oliver.s...@intel.com
# timeout set to 300
# selftests: vDSO: vdso_standalone_test_x86
# Segmentation fault
not ok 5 selftests: vDSO: vdso_standalone_test_x86 # exit=139
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240908/202409082121.553d4c89-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v4] lib/math: Add int_pow test suite
Hi Luis,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc6]
[also build test WARNING on linus/master next-20240906]
[cannot apply to akpm-mm/mm-nonmm-unstable]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_pow-test-suite/20240909-065058
base: v6.11-rc6
patch link:
https://lore.kernel.org/r/20240908224901.78595-1-luis.hernandez093%40gmail.com
patch subject: [PATCH v4] lib/math: Add int_pow test suite
config: m68k-allmodconfig
(https://download.01.org/0day-ci/archive/20240909/202409091732.x5cgqkbv-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240909/202409091732.x5cgqkbv-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409091732.x5cgqkbv-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/math/tests/int_pow_kunit.c:22:18: warning: integer constant is so large
>> that it is unsigned
22 | { 2, 63, 9223372036854775808, "Large result"},
| ^~~
vim +22 lib/math/tests/int_pow_kunit.c
12
13 static const struct test_case_params params[] = {
14 { 64, 0, 1, "Power of zero" },
15 { 64, 1, 64, "Power of one"},
16 { 0, 5, 0, "Base zero" },
17 { 1, 64, 1, "Base one" },
18 { 2, 2, 4, "Two squared"},
19 { 2, 3, 8, "Two cubed"},
20 { 5, 5, 3125, "Five raised to the fifth power" },
21 { U64_MAX, 1, U64_MAX, "Max base" },
> 22 { 2, 63, 9223372036854775808, "Large result"},
23 };
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v4] lib/math: Add int_pow test suite
Hi Luis,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc6]
[also build test WARNING on linus/master next-20240909]
[cannot apply to akpm-mm/mm-nonmm-unstable]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_pow-test-suite/20240909-065058
base: v6.11-rc6
patch link:
https://lore.kernel.org/r/20240908224901.78595-1-luis.hernandez093%40gmail.com
patch subject: [PATCH v4] lib/math: Add int_pow test suite
config: arm64-randconfig-002-20240909
(https://download.01.org/0day-ci/archive/20240910/202409100220.g9ghp1te-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
05f5a91d00b02f4369f46d076411c700755ae041)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240910/202409100220.g9ghp1te-...@intel.com/reproduce)
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409100220.g9ghp1te-...@intel.com/
All warnings (new ones prefixed by >>):
>> lib/math/tests/int_pow_kunit.c:22:11: warning: integer literal is too large
>> to be represented in a signed integer type, interpreting as unsigned
>> [-Wimplicitly-unsigned-literal]
22 | { 2, 63, 9223372036854775808, "Large result"},
| ^
1 warning generated.
vim +22 lib/math/tests/int_pow_kunit.c
12
13 static const struct test_case_params params[] = {
14 { 64, 0, 1, "Power of zero" },
15 { 64, 1, 64, "Power of one"},
16 { 0, 5, 0, "Base zero" },
17 { 1, 64, 1, "Base one" },
18 { 2, 2, 4, "Two squared"},
19 { 2, 3, 8, "Two cubed"},
20 { 5, 5, 3125, "Five raised to the fifth power" },
21 { U64_MAX, 1, U64_MAX, "Max base" },
> 22 { 2, 63, 9223372036854775808, "Large result"},
23 };
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linux-next:master] [list] 17640748eb: kunit.list-kunit-test.fail
Hello,
kernel test robot noticed "kunit.list-kunit-test.fail" on:
commit: 17640748eb3875e486805e2d98ca1044a3a69b93 ("list: test: fix tests for
list_cut_position()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 5acd9952f95fb4b7da6d09a3be39195a80845eb6]
in testcase: kunit
version:
with following parameters:
group: group-00
compiler: gcc-12
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with
16G 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
| Closes:
https://lore.kernel.org/oe-lkp/202409161554.6c3e8d5d-oliver.s...@intel.com
below 2 cases can pass on parent but fail on this commit.
13a6473783aaced3 17640748eb3875e486805e2d98c
---
fail:runs %reproductionfail:runs
| | |
:9 67% 6:6
kunit.list-kunit-test.list_test_list_cut_before.fail
:9 67% 6:6
kunit.list-kunit-test.list_test_list_cut_position.fail
[ 143.881460] KTAP version 1
[ 143.884865] 1..3
[ 143.887802] KTAP version 1
[ 143.891541] # Subtest: list-kunit-test
[ 143.896316] # module: list_test
[ 143.896336] 1..39
[ 143.904046] ok 1 list_test_list_init
[ 143.904607] ok 2 list_test_list_add
[ 143.909698] ok 3 list_test_list_add_tail
[ 143.915034] ok 4 list_test_list_del
[ 143.920415] ok 5 list_test_list_replace
[ 143.925428] ok 6 list_test_list_replace_init
[ 143.930900] ok 7 list_test_list_swap
[ 143.936712] ok 8 list_test_list_del_init
[ 143.941952] ok 9 list_test_list_del_init_careful
[ 143.947363] ok 10 list_test_list_move
[ 143.953422] ok 11 list_test_list_move_tail
[ 143.958536] ok 12 list_test_list_bulk_move_tail
[ 143.964192] ok 13 list_test_list_is_head
[ 143.970279] ok 14 list_test_list_is_first
[ 143.975777] ok 15 list_test_list_is_last
[ 143.981871] ok 16 list_test_list_empty
[ 143.987375] ok 17 list_test_list_empty_careful
[ 143.992611] ok 18 list_test_list_rotate_left
[ 143.998511] ok 19 list_test_list_rotate_to_front
[ 144.004367] ok 20 list_test_list_is_singular
[ 144.010375] # list_test_list_cut_position: EXPECTATION FAILED at
lib/list-test.c:409
Expected cur == &entries[i], but
cur == c9000126fd70
&entries[i] == c9000126fd50
[ 144.016196] not ok 21 list_test_list_cut_position
[ 144.040950] # list_test_list_cut_before: EXPECTATION FAILED at
lib/list-test.c:440
Expected cur == &entries[i], but
cur == c9000129fd60
&entries[i] == c9000129fd50
[ 144.047033] # list_test_list_cut_before: EXPECTATION FAILED at
lib/list-test.c:440
Expected cur == &entries[i], but
cur == c9000129fd70
&entries[i] == c9000129fd60
[ 144.071616] not ok 22 list_test_list_cut_before
[ 144.096387] ok 23 list_test_list_splice
[ 144.102425] ok 24 list_test_list_splice_tail
[ 144.107897] ok 25 list_test_list_splice_init
[ 144.113704] ok 26 list_test_list_splice_tail_init
[ 144.119664] ok 27 list_test_list_entry
[ 144.126022] ok 28 list_test_list_entry_is_head
[ 144.131275] ok 29 list_test_list_first_entry
[ 144.137246] ok 30 list_test_list_last_entry
[ 144.143084] ok 31 list_test_list_first_entry_or_null
[ 144.148823] ok 32 list_test_list_next_entry
[ 144.155283] ok 33 list_test_list_prev_entry
[ 144.161048] ok 34 list_test_list_for_each
[ 144.166792] ok 35 list_test_list_for_each_prev
[ 144.172318] ok 36 list_test_list_for_each_safe
[ 144.178278] ok 37 list_test_list_for_each_prev_safe
[ 144.184235] ok 38 list_test_list_for_each_entry
[ 144.190607] ok 39 list_test_list_for_each_entry_reverse
[ 144.196199] # list-kunit-test: pass:37 fail:2 skip:0 total:39
[ 144.202470] # Totals: pass:37 fail:2 skip:0 total:39
[ 144.208908] not ok 1 list-kunit-test
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240916/202409161554.6c3e8d5d-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH kselftest 3/3] selftests: vDSO: improve getrandom and chacha error messages
Hi Jason,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.12-rc1
next-20241004]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Jason-A-Donenfeld/selftests-vDSO-condition-chacha-build-on-chacha-implementation/20241003-111508
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:
https://lore.kernel.org/r/20241003031307.2236454-4-Jason%40zx2c4.com
patch subject: [PATCH kselftest 3/3] selftests: vDSO: improve getrandom and
chacha error messages
:: branch date: 2 days ago
:: commit date: 2 days ago
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410051432.uazav7yv-...@intel.com/reproduce)
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
| Closes: https://lore.kernel.org/r/202410051432.uazav7yv-...@intel.com/
All warnings (new ones prefixed by >>):
>> vdso_test_getrandom.c:274:3: warning: add explicit braces to avoid dangling
>> else [-Wdangling-else]
274 | else if (WSTOPSIG(status) == (SIGTRAP | 0x80)) {
| ^
1 warning generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 4/4] KVM: selftests: Add bus lock exit test
Hi Manali, kernel test robot noticed the following build warnings: [auto build test WARNING on efbc6bd090f48ccf64f7a8dd5daea775821d57ec] url: https://github.com/intel-lab-lkp/linux/commits/Manali-Shukla/x86-cpufeatures-Add-CPUID-feature-bit-for-the-Bus-Lock-Threshold/20241004-133639 base: efbc6bd090f48ccf64f7a8dd5daea775821d57ec patch link: https://lore.kernel.org/r/20241004053341.5726-5-manali.shukla%40amd.com patch subject: [PATCH v3 4/4] KVM: selftests: Add bus lock exit test :: branch date: 2 days ago :: commit date: 2 days ago compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241006/202410060638.zxrqibij-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/r/202410060638.zxrqibij-...@intel.com/ All warnings (new ones prefixed by >>): x86_64/kvm_buslock_test.c: In function 'buslock_add': >> x86_64/kvm_buslock_test.c:36:39: warning: taking address of packed member of >> 'struct buslock_test' may result in an unaligned pointer value >> [-Waddress-of-packed-member] 36 | buslock_atomic_add(2, &test.val); | ^ At top level: cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] lib/math: Add int_sqrt test suite
Hi Luis, kernel test robot noticed the following build errors: [auto build test ERROR on v6.12-rc4] [also build test ERROR on linus/master] [cannot apply to akpm-mm/mm-nonmm-unstable next-20241025] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_sqrt-test-suite/20241025-035643 base: v6.12-rc4 patch link: https://lore.kernel.org/r/20241024195511.72674-1-luis.hernandez093%40gmail.com patch subject: [PATCH v2] lib/math: Add int_sqrt test suite config: i386-buildonly-randconfig-001-20241026 (https://download.01.org/0day-ci/archive/20241026/202410260709.2xvfasbv-...@intel.com/config) compiler: clang version 19.1.2 (https://github.com/llvm/llvm-project 7ba7d8e2f7b6445b60679da826210cdde29eaf8b) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241026/202410260709.2xvfasbv-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410260709.2xvfasbv-...@intel.com/ All errors (new ones prefixed by >>): >> lib/math/tests/int_sqrt_kunit.c:7:10: fatal error: 'limits.h' file not found 7 | #include | ^~ 1 error generated. Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for GET_FREE_REGION Depends on [n]: SPARSEMEM [=n] Selected by [y]: - RESOURCE_KUNIT_TEST [=y] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y] vim +7 lib/math/tests/int_sqrt_kunit.c 2 3 #include 4 #include 5 #include 6 #include > 7 #include 8 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] lib/math: Add int_sqrt test suite
Hi Luis, kernel test robot noticed the following build errors: [auto build test ERROR on v6.12-rc4] [also build test ERROR on linus/master] [cannot apply to akpm-mm/mm-nonmm-unstable next-20241025] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Luis-Felipe-Hernandez/lib-math-Add-int_sqrt-test-suite/20241025-035643 base: v6.12-rc4 patch link: https://lore.kernel.org/r/20241024195511.72674-1-luis.hernandez093%40gmail.com patch subject: [PATCH v2] lib/math: Add int_sqrt test suite config: m68k-sun3_defconfig (https://download.01.org/0day-ci/archive/20241026/202410260915.z3q6zogs-...@intel.com/config) compiler: m68k-linux-gcc (GCC) 13.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241026/202410260915.z3q6zogs-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410260915.z3q6zogs-...@intel.com/ All errors (new ones prefixed by >>): >> lib/math/tests/int_sqrt_kunit.c:7:10: fatal error: limits.h: No such file or >> directory 7 | #include | ^~ compilation terminated. Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for GET_FREE_REGION Depends on [n]: SPARSEMEM [=n] Selected by [m]: - RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m] vim +7 lib/math/tests/int_sqrt_kunit.c 2 3 #include 4 #include 5 #include 6 #include > 7 #include 8 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 2/9] initramfs_test: kunit tests for initramfs unpacking
Hi David, kernel test robot noticed the following build warnings: [auto build test WARNING on akpm-mm/mm-nonmm-unstable] [also build test WARNING on brauner-vfs/vfs.all linus/master v6.12-rc6 next-20241108] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/David-Disseldorp/init-add-initramfs_internal-h/20241107-083002 base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable patch link:https://lore.kernel.org/r/20241107002044.16477-3-ddiss%40suse.de patch subject: [PATCH v3 2/9] initramfs_test: kunit tests for initramfs unpacking config: sh-randconfig-r122-20241108 (https://download.01.org/0day-ci/archive/20241109/202411090808.exzphnlj-...@intel.com/config) compiler: sh4-linux-gcc (GCC) 14.2.0 reproduce: (https://download.01.org/0day-ci/archive/20241109/202411090808.exzphnlj-...@intel.com/reproduce) 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 | Closes: https://lore.kernel.org/oe-kbuild-all/202411090808.exzphnlj-...@intel.com/ All warnings (new ones prefixed by >>, old ones prefixed by <<): >> WARNING: modpost: vmlinux: section mismatch in reference: >> initramfs_test_cases+0x0 (section: .data) -> set_reset_devices (section: >> .init.text) WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x1c (section: .data) -> set_reset_devices (section: .init.text) WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x38 (section: .data) -> set_reset_devices (section: .init.text) WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x54 (section: .data) -> set_reset_devices (section: .init.text) WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x70 (section: .data) -> set_reset_devices (section: .init.text) WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x8c (section: .data) -> set_reset_devices (section: .init.text) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
