[lkml]   [2007]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Thread flags modified without set_thread_flag() (non atomically)
    [trimming cc list since I'm only replying to the avr32 part]

    On Wed, 28 Feb 2007 22:03:49 -0800
    Andrew Morton <> wrote:

    > On Mon, 26 Feb 2007 12:10:37 -0800 Mathieu Desnoyers <> wrote:

    > > avr32/kernel/ptrace.c: ti->flags |= _TIF_BREAKPOINT;
    > No, I don't immediately see anything in the flush_old_exec() code path
    > which tells us that nobody else can look up this thread_info (or be holding
    > a ref to it) in this context.
    > > avr32/kernel/ptrace.c: ti->flags |= TIF_SINGLE_STEP;
    > heh. Haarvard, you got a bug.

    Heh, yeah. That would indeed explain some strange gdb behaviour. It
    will only trigger when single-stepping into an exception or interrupt
    handler so thanks for pointing it out; I would have had a hard time
    figuring it out on my own...

    I don't think either of those need to be atomic though, since both of
    them happen in monitor mode with interrupts disabled.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-03-01 10:37    [W:0.029 / U:31.876 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site