linux-kernel - Re: "BUG: MAX_STACK_TRACE_ENTRIES too low!"

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] [day] [month] [year] [list]

Date:	Sun, 14 Dec 2008 13:54:22 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: "BUG: MAX_STACK_TRACE_ENTRIES too low!" - reason for concern?

Peter Zijlstra wrote:
> On Sun, 2008-12-14 at 02:38 +0100, Stefan Richter wrote:
[unload/ reload drivers]
>> Dec 14 01:23:29 stein BUG: MAX_STACK_TRACE_ENTRIES too low!
> 
> lockdep resource allocation is pretty simple wrt to modules, it will not
> re-use anything, therefore cycling modules will let it run out of its
> resources pretty quickly.
> 
> I suppose one could go add all kinds of smart and complicate the whole
> thing, but I'm not sure its worth it.

OK, no problem.  I have another test PC which I apparently reboot often
enough to stay under this limit.  Thanks for the clarification.
-- 
Stefan Richter
-=====-==--- ==-- -===-
http://arcgraph.de/sr/
--
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/