linux-kernel - [PATCH] Increase MAX_STACK_TRACE

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

Date:	Mon, 21 Sep 2009 19:13:00 +0200 (CEST)
From:	John Kacur <jkacur@...hat.com>
To:	mingo@...e.hu, tglx@...uxtronix.de
cc:	linux-kernel@...r.kernel.org, Clark Williams <williams@...hat.com>
Subject: [PATCH] Increase MAX_STACK_TRACE_ENTRIES


Ingo: please consider this patch if there are no negative consequences to 
increasing this value. It fixes a problem that we have seen in the past on
(at least) the real-time kernel. (BUG: MAX_STACK_TRACE_ENTRIES).

This patch applies to the current tip/master

Thank You

Author: Clark Williams <williams@...hat.com>
Date: Mon, 21 Sep 2009 18:29:30 +0200
Subject: [PATCH] Increase MAX_STACK_TRACE_ENTRIES to compensate for lockdep and debug options eating up backtrace slots.

    Signed-off-by: Clark Williams <williams@...hat.com>
    Signed-off-by: John Kacur <jkacur@...hat.com>
---
 kernel/lockdep_internals.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/lockdep_internals.h b/kernel/lockdep_internals.h
index a2ee95a..953745c 100644
--- a/kernel/lockdep_internals.h
+++ b/kernel/lockdep_internals.h
@@ -65,7 +65,7 @@ enum {
  * Stack-trace: tightly packed array of stack backtrace
  * addresses. Protected by the hash_lock.
  */
-#define MAX_STACK_TRACE_ENTRIES	262144UL
+#define MAX_STACK_TRACE_ENTRIES	393216UL
 
 extern struct list_head all_lock_classes;
 extern struct lock_chain lock_chains[];
-- 
1.6.0.6


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