linux-kernel - [PATCH 0/1] powerpc: Fix kuap warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260109064917.777587-1-sshegde@linux.ibm.com>
Date: Fri,  9 Jan 2026 12:19:16 +0530
From: Shrikanth Hegde <sshegde@...ux.ibm.com>
To: maddy@...ux.ibm.com, linuxppc-dev@...ts.ozlabs.org, rostedt@...dmis.org,
        mhiramat@...nel.org
Cc: sshegde@...ux.ibm.com, chleroy@...nel.org, riteshh@...ux.ibm.com,
        linux-kernel@...r.kernel.org, hbathini@...ux.ibm.com
Subject: [PATCH 0/1] powerpc: Fix kuap warnings

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