Commen=
t # 13
on bug 99275<=
/a>
from Reimar Imhof
after I've had seen, 4.8 hat the same problem I tried to find =
the first good
4.8.x:
> git bisect new
107d026ae1c80ac0881f791a58cd115321d111ca is the first new commit
commit 107d026ae1c80ac0881f791a58cd115321d111ca
Author: Will Deacon <will.dea=
con@arm.com>
Date: Fri Aug 26 11:36:39 2016 +0100
arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
commit 3a402a709500c5a3faca2111668c33d96555e35a upstream.
When TIF_SINGLESTEP is set for a task, the single-step state machine is
enabled and we must take care not to reset it to the active-not-pending
state if it is already in the active-pending state.
Unfortunately, that's exactly what user_enable_single_step does, by
unconditionally setting the SS bit in the SPSR for the current task.
This causes failures in the GDB testsuite, where GDB ends up missing
expected step traps if the instruction being stepped generates another
trap, e.g. PTRACE_EVENT_FORK from an SVC instruction.
This patch fixes the problem by preserving the current state of the
stepping state machine when TIF_SINGLESTEP is set on the current thread.
Cc: <stable@vger.k=
ernel.org>
Reported-by: Yao Qi <yao.qi=
4;arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
:040000 040000 98b6a8a0d27ab29b17b6b617e52beb33d56dc604
46030e41ff5783555a6d6e895799aabbe3a0c46e M arch