On 11/03, Peter Zijlstra wrote:
>
> ======================================================
> [ INFO: soft-safe -> soft-unsafe lock order detected ]
> 2.6.19-rc4 #1
> ------------------------------------------------------
> mm_tester/1875 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> (&tsk->delays->lock){--..}, at: [<c0156652>] __delayacct_add_tsk+0x131/0x1d3
>
> and this task is already holding:
> (&sighand->siglock){.+..}, at: [<c0156b69>] taskstats_exit_send+0x52/0x3b2
> which would create a new lock dependency:
> (&sighand->siglock){.+..} -> (&tsk->delays->lock){--..}
Thanks.
I introduced this bug in
"[PATCH 5/6] taskstats: kill ->taskstats_lock in favor of ->siglock"
Oleg.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
