2021-11-19 10:09:57

by Zhou, Jie2X

[permalink] [raw]
Subject: kernel-selftests/lkdtm: USERCOPY_STACK_FRAME_TO fail

hi,
LKP test try to test kernel selftests/lkdtm.
But I got some error like following:

# [ 107.625978] lkdtm: ok: SMEP did not get cleared
# [ 107.625980] lkdtm: trying to clear SMEP with call gadget
# [ 107.625983] lkdtm: ok: SMEP removal was reverted
# UNSET_SMEP: saw 'pinned CR4 bits changed:': ok
ok 15 selftests: lkdtm: UNSET_SMEP.sh

# [ 108.321689] lkdtm: Performing direct entry SLAB_LINEAR_OVERFLOW
#
# [ 108.333630] lkdtm: Attempting slab linear overflow ...
# SLAB_LINEAR_OVERFLOW: missing 'call trace:': [FAIL]
not ok 19 selftests: lkdtm: SLAB_LINEAR_OVERFLOW.sh # exit=1

# READ_AFTER_FREE: missing 'call trace:|Memory correctly poisoned': [FAIL]
not ok 22 selftests: lkdtm: READ_AFTER_FREE.sh # exit=1

# READ_BUDDY_AFTER_FREE: missing 'call trace:|Memory correctly poisoned': [FAIL]
not ok 24 selftests: lkdtm: READ_BUDDY_AFTER_FREE.sh # exit=1

# USERCOPY_STACK_FRAME_TO: missing 'call trace:': [FAIL]
not ok 69 selftests: lkdtm: USERCOPY_STACK_FRAME_TO.sh # exit=1

# USERCOPY_STACK_FRAME_FROM: missing 'call trace:': [FAIL]
not ok 70 selftests: lkdtm: USERCOPY_STACK_FRAME_FROM.sh # exit=1

# STACKLEAK_ERASING: missing 'OK: the rest of the thread stack is properly erased': [FAIL]
not ok 73 selftests: lkdtm: STACKLEAK_ERASING.sh # exit=1

# CFI_FORWARD_PROTO: missing 'call trace:': [FAIL]
not ok 74 selftests: lkdtm: CFI_FORWARD_PROTO.sh # exit=1

# FORTIFIED_SUBOBJECT: missing 'call trace:': [FAIL]
not ok 77 selftests: lkdtm: FORTIFIED_SUBOBJECT.sh # exit=1

Am I missing something special(kconfig, packages etc). ?

My kernel is v5.15

best regards,