Re: 2.6.2-rc1-mm2 (msp34xx badness in sched.c)

[David Woodhouse]

On Sat, 2004-01-24 at 23:47 +0100, Tony Vroon wrote:
> sleep_on called without kernel_lock, from what it looks like in msp34xx.

Fairly typical example of the type of error the additional check was
expected to find. Note also that the same thread should be using
complete_and_exit().

I suspect some of the instances of del_timer() should be
del_timer_sync() too. Particularly in msp_wake_thread() and
map_detach().

Is there something we can do to make del_timer() break when it should
have been del_timer_sync()... like waiting five seconds and then
deliberately calling it on another CPU? :)

> Badness in interruptible_sleep_on at kernel/sched.c:2230
> Call Trace:
>  [<c011ed24>] interruptible_sleep_on+0xf4/0x100
>  [<c011e950>] default_wake_function+0x0/0x20
>  [<c02b9a27>] msp3410d_thread+0xa7/0x680
>  [<c02b9980>] msp3410d_thread+0x0/0x680
>  [<c0108e69>] kernel_thread_helper+0x5/0xc

-- 
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/