linux-kernel - Re: 2.6.19-rc3: more DWARFs and strange messages

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: <4549CA86.76E4.0078.0@novell.com>
Date:	Thu, 02 Nov 2006 09:37:58 +0000
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Martin Lorenz" <martin@...enz.eu.org>, "Andi Kleen" <ak@...e.de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages

>what is a reasonable kstack parameter to be informative for you?

This unfortunately depends on the depth of the stack that is in use
at the point the dump is taken. The only safe value would be to
dump the full stack size (kstack=1024 for 4k stack, kstack=2048
for 8k ones), but since it'll stop at a stack boundary perhaps that's
what you should go with.

As to Andi's remark regarding WARN_ON() - you'd have to address
that issue in a private patch first, or the addition of the kstack=
parameter will be useless. I presume it's likely you don't have the
time to do that...

Jan
-
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/