mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-12 13:55:32 +00:00
[AVR32] Fix bogus ti->flags manipulation in debug handler
We should OR in a bitmask, not a bit offset, into ti->flags. This might fix some strange behaviour when single stepping. Also, use set_ti_thread_flag() to manipulate the flags to avoid surprises in the future. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
This commit is contained in:
parent
bfa4f55cc8
commit
a19b4a1405
1 changed files with 2 additions and 2 deletions
|
@ -313,7 +313,7 @@ asmlinkage void do_debug_priv(struct pt_regs *regs)
|
|||
__mtdr(DBGREG_DC, dc);
|
||||
|
||||
ti = current_thread_info();
|
||||
ti->flags |= _TIF_BREAKPOINT;
|
||||
set_ti_thread_flag(ti, TIF_BREAKPOINT);
|
||||
|
||||
/* The TLB miss handlers don't check thread flags */
|
||||
if ((regs->pc >= (unsigned long)&itlb_miss)
|
||||
|
@ -328,7 +328,7 @@ asmlinkage void do_debug_priv(struct pt_regs *regs)
|
|||
* single step.
|
||||
*/
|
||||
if ((regs->sr & MODE_MASK) != MODE_SUPERVISOR)
|
||||
ti->flags |= TIF_SINGLE_STEP;
|
||||
set_ti_thread_flag(ti, TIF_SINGLE_STEP);
|
||||
} else {
|
||||
panic("Unable to handle debug trap at pc = %08lx\n",
|
||||
regs->pc);
|
||||
|
|
Loading…
Reference in a new issue