Recently stumbled upon these kuap warnings. This happens with preempt=full/lazy kernel with function tracing enabled. What irked me was kernel compilation was getting failed when i had tracing enabled. It doesn't fail everytime. While running stress-ng memory class it threw same warnings. So that helped to narrow it down. So one possible way is to disable tracing for these enter/exit vmx_usercopy. That seems to fix the bug/warnings. But that will make them as non trace-able. If there is a better way to fix these warning while keeping them as trace-able, please let me know.
Anyone with insights on amr, vmx and tracing, please advise. Shrikanth Hegde (1): powerpc: Fix kuap warnings on lazy/full preemption with tracing arch/powerpc/kernel/process.c | 10 +++++----- arch/powerpc/lib/vmx-helper.c | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) -- 2.47.3
