From 2fed44a5053835baecc335ba3f395272b658ff98 Mon Sep 17 00:00:00 2001 From: ae Date: Wed, 5 Aug 2015 10:59:59 +0000 Subject: MFC r285888: Build debug version of rmlock's methods only when LOCK_DEBUG > 0. Currently LOCK_DEBUG is always defined in sys/lock.h (0 or 1). This means that debugging code always built. In addition the kernel modules have always defined LOCK_DEBUG as 1. So, debugging rmlock code is always used by kernel modules. --- sys/kern/kern_rmlock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys/kern/kern_rmlock.c') diff --git a/sys/kern/kern_rmlock.c b/sys/kern/kern_rmlock.c index ec0e7fa..1ac08de 100644 --- a/sys/kern/kern_rmlock.c +++ b/sys/kern/kern_rmlock.c @@ -581,7 +581,7 @@ _rm_wunlock(struct rmlock *rm) mtx_unlock(&rm->rm_lock_mtx); } -#ifdef LOCK_DEBUG +#if LOCK_DEBUG > 0 void _rm_wlock_debug(struct rmlock *rm, const char *file, int line) -- cgit v1.1