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
| ||
|
Date: Tue, 06 Dec 2022 14:12:01 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org Cc: Masami Hiramatsu <mhiramat@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Karol Herbst <karolherbst@...il.com>, Pekka Paalanen <ppaalanen@...il.com>, Dave Hansen <dave.hansen@...ux.intel.com>, Andy Lutomirski <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, x86@...nel.org Subject: [PATCH 0/2] x86/mm/kmmio: Have mmiotracer play nice with lockdep The mmiotrace tracer is "special". The purpose is to help reverse engineer binary drivers by removing the memory allocated by the driver and when the driver goes to access it, a fault occurs, the mmiotracer will record what the driver was doing and then do the work on its behalf by single stepping through the process. But to achieve this ability, it must do some special things. One is it needs to grab a lock while in the breakpoint handler. This is considered an NMI state, and then lockdep warns that the lock is being held in both an NMI state (really a breakpoint handler) and also in normal context. As the breakpoint/NMI state only happens when the driver is accessing memory, there's no concern of a race condition against the setup and tear-down of mmiotracer. To make lockdep and mmiotrace work together, convert the locks used in the breakpoint handler into arch_spin_lock(). It also takes the rcu_read_lock() at the fault, and releases it in the single step breakpoint. This makes lockdep sad. Luckily, it also disables preemption when taking the rcu_read_lock() and enables it when releasing the rcu_read_lock(). As now the sched RCU variant is basically the same as the "normal" RCU variant, there's no reason to take the rcu_read_lock(), so just remove it. Steven Rostedt (2): x86/mm/kmmio: Switch to arch_spin_lock() x86/mm/kmmio: Remove rcu_read_lock() ---- arch/x86/mm/kmmio.c | 34 ++++++++++++++++++++++------------ 1 file changed, 22 insertions(+), 12 deletions(-)
Powered by blists - more mailing lists