public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Eric Rannaud <eric.rannaud@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
	nagar@watson.ibm.com, Chandra Seetharaman <sekharan@us.ibm.com>,
	Andi Kleen <ak@suse.de>, Jan Beulich <jbeulich@novell.com>
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
Date: Sat, 30 Sep 2006 21:21:17 +0100	[thread overview]
Message-ID: <20060930202117.GO29920@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0609301237460.3952@g5.osdl.org>

On Sat, Sep 30, 2006 at 12:54:21PM -0700, Linus Torvalds wrote:
> We need Al Viro here to put this kind of code into perspective. I _think_ 
> he would have some choice words for code that is meant to "help" 
> debugging, and is this horrible.

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

  reply	other threads:[~2006-09-30 20:21 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 19:20 BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Eric Rannaud
2006-09-30 19:49 ` Peter Zijlstra
2006-09-30 20:23   ` Linus Torvalds
2006-09-30 20:57   ` Eric Rannaud
2006-09-30 19:54 ` Linus Torvalds
2006-09-30 20:21   ` Al Viro [this message]
2006-09-30 20:28     ` Linus Torvalds
2006-09-30 20:30   ` Andi Kleen
2006-09-30 20:47     ` Linus Torvalds
2006-09-30 20:49       ` Ingo Molnar
2006-09-30 21:11         ` Linus Torvalds
2006-09-30 21:25           ` Ingo Molnar
2006-09-30 21:57           ` Andi Kleen
2006-09-30 22:09             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) II Andi Kleen
2006-09-30 22:19               ` Eric Rannaud
2006-09-30 22:24                 ` Andi Kleen
2006-09-30 22:54             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Linus Torvalds
2006-10-04  9:21           ` Jan Beulich
2006-10-04 15:12             ` Linus Torvalds
2006-09-30 21:43     ` Eric Rannaud
2006-09-30 22:03       ` Andi Kleen
2006-09-30 21:56     ` Linus Torvalds
2006-09-30 22:02       ` Andi Kleen
2006-09-30 22:10         ` Ingo Molnar
2006-09-30 22:23           ` Andi Kleen
2006-09-30 22:55         ` Linus Torvalds
2006-09-30 22:59           ` Linus Torvalds
2006-09-30 23:56           ` Andi Kleen
2006-10-01  0:25             ` Linus Torvalds
2006-10-01  0:51               ` Linus Torvalds
2006-10-01  9:27                 ` Andi Kleen
2006-10-04  9:25     ` Jan Beulich
2006-10-04 10:52       ` Andi Kleen
2006-10-04 11:58         ` Jan Beulich
2006-10-04 12:03           ` Andi Kleen
2006-10-04 12:10             ` Jan Beulich
2006-09-30 20:43   ` Linus Torvalds
2006-10-04  9:15   ` Jan Beulich
2006-09-30 20:13 ` Andrew Morton
2006-09-30 20:52   ` Eric Rannaud
2006-09-30 21:04     ` Andrew Morton
2006-09-30 22:00       ` Eric Rannaud
2006-09-30 22:05         ` Ingo Molnar
2006-10-01  0:59           ` Eric Rannaud

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060930202117.GO29920@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=eric.rannaud@gmail.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nagar@watson.ibm.com \
    --cc=sekharan@us.ibm.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox