Commit e0aa3a66 authored by Russell King's avatar Russell King
Browse files

ARM: entry: ensure that IRQs are enabled when calling syscall_trace_exit()



The audit code looks like it's been written to cope with being called
with IRQs enabled.  However, it's unclear whether IRQs should be
enabled or disabled when calling the syscall tracing infrastructure.

Right now, sometimes we call this with IRQs enabled, and other times
with IRQs disabled.  Opt for IRQs being enabled for consistency.
Acked-by: default avatarWill Deacon <will.deacon@arm.com>
Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
parent 3302cadd
...@@ -275,7 +275,7 @@ __sys_trace_return: ...@@ -275,7 +275,7 @@ __sys_trace_return:
b ret_slow_syscall b ret_slow_syscall
__sys_trace_return_nosave: __sys_trace_return_nosave:
asm_trace_hardirqs_off save=0 enable_irq_notrace
mov r0, sp mov r0, sp
bl syscall_trace_exit bl syscall_trace_exit
b ret_slow_syscall b ret_slow_syscall
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment