Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: Linus Torvalds <torvalds@xxxxxxxx>
- Date: Sat, 30 Sep 2006 13:28:14 -0700 (PDT)
On Sat, 30 Sep 2006, Al Viro wrote:
Oh, so _that_ is what it is supposed to do? I've seen it when it went
in, tried to read, barfed and chalked it up to KDB or itanic braindamage
(both have turds of that genre). Didn't realize that lockdep used it too...
Well, anything that shows or needs a back-trace. By definition, it's
pretty much just debug code.
I sure as hell hope we don't have any actual _semantics_ that depend on
back-traces, like the broken asynchronous C++ exception handling code etc
that people have in user space (what a total brain-damage _that_ is!).
Linus
-
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/
- References:
- BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: Eric Rannaud
- Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: Linus Torvalds
- Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: Al Viro
- BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Prev by Date: Re: GPLv3 Position Statement
- Next by Date: Re: 2.6.18-mm2
- Previous by thread: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Next by thread: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Index(es):