>> The lockdep warning in itself is probably valid, but the reason for the
>> _hang_ is the
>>
>> [ 138.831385] Unable to handle kernel paging request at ffffffff82800000 RIP:
>> [ 138.831439] [<ffffffff8020b491>] show_trace+0x311/0x380
>>
>> and that code is just a total mess.
>
>The code decides to do a fallback at the top of stack space for some reason.
>
>Hmm, i've seen this working on other kernel threads, but maybe
>that was luck. Kernel threads don't end up in user space
>so the normal check for that doesn't work.
>I guess we just need another termination for the kernel threads
>by pushing a 0 there explicitely. Jan, do you agree?
I thought we had done this already.
>> > [ 138.751306] [<ffffffff8021ecc0>] search_extable+0x40/0x70
>
>After here the unwinder seems to become a bit and it shouldn't print
>multiple entries. Jan any ideas why?
Not without raw stack contents.
>Proposed patch appended. Jan, what do you think?
As said above - I thought we added zero-termination already.
Jan
-
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]
