linux-kernel - [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable

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]

Date:	Wed, 22 Jul 2009 20:58:32 +0800
From:	tom.leiming@...il.com
To:	a.p.zijlstra@...llo.nl
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	mingo@...e.hu, torvalds@...ux-foundation.org,
	Ming Lei <tom.leiming@...il.com>
Subject: [tip:core/locking 2/3] lockdep:define preallocated "stack" for BFS as per cpu variable

From: Ming Lei <tom.leiming@...il.com>

Signed-off-by: Ming Lei <tom.leiming@...il.com>
---
 kernel/lockdep.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index 1b1796a..1583439 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -847,7 +847,7 @@ struct circular_queue {
 	unsigned int  front, rear;
 };
 
-static struct circular_queue lock_cq;
+static DEFINE_PER_CPU(struct circular_queue, lock_cq);
 
 unsigned int max_bfs_queue_depth;
 
@@ -937,7 +937,7 @@ static int __bfs(struct lock_list *source_entry,
 {
 	struct lock_list *entry;
 	struct list_head *head;
-	struct circular_queue *cq = &lock_cq;
+	struct circular_queue *cq = &get_cpu_var(lock_cq);
 	int ret = 1;
 
 	if (match(source_entry, data)) {
@@ -993,6 +993,7 @@ static int __bfs(struct lock_list *source_entry,
 		}
 	}
 exit:
+	put_cpu_var(lock_cq);
 	return ret;
 }
 
-- 
1.6.0.GIT

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