Re: [PATCH v4] sched/numa: fix unsafe get_task_struct() in task_numa_assign()

From: Sasha Levin
Date: Mon Nov 10 2014 - 11:10:11 EST


On 11/10/2014 11:03 AM, Peter Zijlstra wrote:
> On Fri, Nov 07, 2014 at 10:48:27PM -0500, Sasha Levin wrote:
>> [ 829.539183] BUG: spinlock recursion on CPU#10, trinity-c594/11067
>> [ 829.539203] lock: 0xffff880631dd6b80, .magic: dead4ead, .owner: trinity-c594/11067, .owner_cpu: 13
>
> Ooh, look at that. CPU#10 vs .owner_cpu: 13 on the _same_ task.
>
> One of those again :/

Hum. I missed that one.

Hold on, but the magic here is fine and the owner pointer is fine, why would just the owner cpu
be wrong?


Thanks,
Sasha

--
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/