From: Andrew Morton <akpm@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Jan Beulich <jbeulich@novell.com>
Cc: ak@suse.de, mingo@elte.hu, arjan@infradead.org,
Matt_Domsch@dell.com, davem@davemloft.net,
yoshfuji@linux-ipv6.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [IPV6]: Audit all ip6_dst_lookup/ip6_dst_store calls
Date: Tue, 1 Aug 2006 07:41:33 -0700 [thread overview]
Message-ID: <20060801074133.b5b96f11.akpm@osdl.org> (raw)
In-Reply-To: <20060731090433.GA25192@gondor.apana.org.au>
On Mon, 31 Jul 2006 19:04:33 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> 2) There is something broken in the x86_64 unwind code which is causing
> it to panic just about everytime somebody calls dump_stack().
>
> Andi, this is the second time I've seen a report where an otherwise
> harmless dump_stack call (the other one was caused by a WARN_ON) gets
> turned into a panic by the stack unwind code on x86_64. This particular
> report is with 2.6.18-rc3 so it looks like whatever bug is causing it
> hasn't been fixed yet.
>
> Could you please have a look at it? Thanks.
Jan thinks this might have been fixed by a patch which he sent Andi a
couple of days ago. Andi has sent that patch to Linus but I'm not sure
which patch it was and I'm not sure whether it has been merged into
mainline.
But yes, -rc3 unwind has problems.
next prev parent reply other threads:[~2006-08-01 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:45 lockdep tcp_v6_rcv message Matt Domsch
2006-07-29 4:33 ` [IPV6]: Audit all ip6_dst_lookup/ip6_dst_store calls Herbert Xu
2006-07-30 22:44 ` David Miller
2006-07-31 3:32 ` Matt Domsch
2006-07-31 3:56 ` David Miller
2006-07-31 4:25 ` Matt Domsch
2006-07-31 9:04 ` Herbert Xu
2006-08-01 14:41 ` Andrew Morton [this message]
2006-08-01 17:24 ` Andi Kleen
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=20060801074133.b5b96f11.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®