All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Christian Weiske <cweiske@cweiske.de>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	reiserfs-dev@namesys.com, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a
Date: Sun, 24 Sep 2006 19:59:34 +0200	[thread overview]
Message-ID: <20060924175934.GA15420@elte.hu> (raw)
In-Reply-To: <20060924031923.76886810.akpm@osdl.org>


* Andrew Morton <akpm@osdl.org> wrote:

> You have tcp_v6 lockdep warnings.  They're in
> http://xml.cweiske.de/dojo%20kernelpanic%20+%20debug.tar.bz2 is anyone is
> keen.  (I've largely lost interest in lockdep warnings - many of them are
> false positives and require make-lockdep-shut-up patches).

FYI, this is from Herbert Xu's recent mail to netdev:

| Subject: Re: neigh_lookup lockdep warning
|
| [...]
| BTW, out of the last four validator reports I've read three have 
| turned out to be genuine bugs.  So you guys have done a fantastic job!

  reply	other threads:[~2006-09-24 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 15:56 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a Christian Weiske
2006-09-23 20:42 ` Andrew Morton
2006-09-23 20:39   ` Ingo Molnar
2006-09-24  9:11   ` Christian Weiske
2006-09-24  9:30     ` Christian Weiske
2006-09-24 10:19     ` Andrew Morton
2006-09-24 17:59       ` Ingo Molnar [this message]
2006-09-24 12:20   ` Christian Weiske
2006-09-24 16:50     ` Andrew Morton
2006-09-24 17:47       ` Christian Weiske
2006-09-25  4:14         ` Nick Piggin
2006-09-25 18:36         ` Christian Weiske
2006-09-25 21:26           ` Andrew Morton
2006-10-02 17:01             ` Christian Weiske
2006-10-03 14:20               ` Christian Weiske

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=20060924175934.GA15420@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=cweiske@cweiske.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=reiserfs-dev@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.