ARM: fix missing syscall trace exit

Josh Stone reports:

I've discovered a case where both arm and arm64 will miss a ptrace
syscall-exit that they should report. If the syscall is entered
without TIF_SYSCALL_TRACE set, then it goes on the fast path. It's
then possible to have TIF_SYSCALL_TRACE added in the middle of the
syscall, but ret_fast_syscall doesn't check this flag again.

Fix this by always checking for a syscall trace in the fast exit path.

Reported-by: Josh Stone <jistone@redhat.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

Changed files
+3 -1
arch
arm
+3 -1
arch/arm/kernel/entry-common.S
··· 33 33 UNWIND(.fnstart ) 34 34 UNWIND(.cantunwind ) 35 35 disable_irq @ disable interrupts 36 - ldr r1, [tsk, #TI_FLAGS] 36 + ldr r1, [tsk, #TI_FLAGS] @ re-check for syscall tracing 37 + tst r1, #_TIF_SYSCALL_WORK 38 + bne __sys_trace_return 37 39 tst r1, #_TIF_WORK_MASK 38 40 bne fast_work_pending 39 41 asm_trace_hardirqs_on