RISC-V: Don't check text_mutex during stop_machine

Browse source

We're currently using stop_machine() to update ftrace & kprobes, which
means that the thread that takes text_mutex during may not be the same
as the thread that eventually patches the code.  This isn't actually a
race because the lock is still held (preventing any other concurrent
accesses) and there is only one thread running during stop_machine(),
but it does trigger a lockdep failure.

This patch just elides the lockdep check during stop_machine.

Fixes: c15ac4fd60 ("riscv/ftrace: Add dynamic function tracer support")
Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Reported-by: Changbin Du <changbin.du@gmail.com>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20230303143754.4005217-1-conor.dooley@microchip.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

...

This commit is contained in:

Conor Dooley 2023-03-03 14:37:55 +00:00 • committed by Palmer Dabbelt

parent 76950340cf

commit 2a8db5ec4a

No known key found for this signature in database

GPG key ID: 2E1319F35FBB1889

4 changed files with 39 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

arch/riscv/include/asm/ftrace.h

View file

2

arch/riscv/include/asm/patch.h

View file

13

arch/riscv/kernel/ftrace.c

View file

28

arch/riscv/kernel/patch.c

View file