Re: lockdep: Warning & NULL ptr deref

[Sasha Levin]

On Tue, Feb 28, 2012 at 5:08 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> On Tue, 2012-02-28 at 16:55 +0200, Sasha Levin wrote:
>> > Hmm, cute, does a kernel without lockdep explode too? If its proper
>> > memory corruption one would expect that.
>>
>> Looks like it only happens when lockdep is there, it also happens in
>> the same lockdep line of code all the time.
>
> OK, that smells.. no good idea then on how this could happen :/

I have some more details which may help:

1. It actually happens almost every time. I stop trinity, trigger
sysrq twice and it shows up. It doesn't happen while trinity is
running.
2. It always happens when trying to print locks held by ksoftirqd ("1
lock held by ksoftirqd/0/3:")
3. If it helps any, the bug we were originally trying to find is that
trinity leaves a bunch of zombie processes, with this kernel stack:


[  328.028320] trinity         x ffff880038eded40  5200  5178      1 0x00000000
[  328.028320]  ffff880037eafd28 0000000000000086 0000000000000001
ffff880037eaffd8
[  328.028320]  00000000001d4340 ffff880037eae000 00000000001d4340
00000000001d4340
[  328.028320]  00000000001d4340 00000000001d4340 ffff880037eaffd8
00000000001d4340
[  328.028320] Call Trace:
[  328.028320]  [<ffffffff826e1c1a>] schedule+0x3a/0x50
[  328.028320]  [<ffffffff810b2251>] do_exit+0x2f1/0x4d0
[  328.028320]  [<ffffffff810b24cc>] do_group_exit+0x5c/0xd0
[  328.028320]  [<ffffffff810c1b1c>] get_signal_to_deliver+0x1dc/0x3d0
[  328.028320]  [<ffffffff8104bcc3>] do_signal+0x53/0x130
[  328.028320]  [<ffffffff81070000>] ? default_init_apic_ldr+0x20/0x70
[  328.028320]  [<ffffffff810e25bd>] ? sub_preempt_count+0x9d/0xd0
[  328.028320]  [<ffffffff826e3366>] ? _raw_spin_unlock_irq+0x46/0x70
[  328.028320]  [<ffffffff826e413f>] ? retint_signal+0x11/0x92
[  328.028320]  [<ffffffff8104be25>] do_notify_resume+0x65/0x80
[  328.028320]  [<ffffffff8187c61e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[  328.028320]  [<ffffffff826e417b>] retint_signal+0x4d/0x92
--
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/