Re: [patch] i386: fix stuck unwind into kernel thread

>>> Chuck Ebbert <[email protected]> 06.08.06 20:56 >>>
>We cannot unwind past kernel_thread_helper.

Just as mentioned before - we shouldn't add endless special cases to the code that interprets the unwind
information, but rather fix the unwind information so that it properly reflect the actual state. Like in the
other case, the piece of code should be properly annotated, which would require it to be moved into
an assembly file (it escapes me why code like that was ever placed in a C file).

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/

---

• Follow-Ups:
  • Re: [patch] i386: fix stuck unwind into kernel thread
    • From: Andi Kleen <[email protected]>

• References:
  • [patch] i386: fix stuck unwind into kernel thread
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
• Next by Date: Re: OHCI and SKIP bit
• Previous by thread: [patch] i386: fix stuck unwind into kernel thread
• Next by thread: Re: [patch] i386: fix stuck unwind into kernel thread
• Index(es):
  • Date
  • Thread

[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]