linux-kernel - Re: [IPV6]: Audit all ip6_dst_lookup/ip6_dst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060801074133.b5b96f11.akpm@osdl.org>
Date:	Tue, 1 Aug 2006 07:41:33 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>,
	Jan Beulich <jbeulich@...ell.com>
Cc:	ak@...e.de, mingo@...e.hu, arjan@...radead.org,
	Matt_Domsch@...l.com, davem@...emloft.net, yoshfuji@...ux-ipv6.org,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [IPV6]: Audit all ip6_dst_lookup/ip6_dst_store calls

On Mon, 31 Jul 2006 19:04:33 +1000
Herbert Xu <herbert@...dor.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/