From 6db89449f0ea9aa9c3edfd4311db652d9417cb9d Mon Sep 17 00:00:00 2001 From: John Baldwin Date: Wed, 23 May 2007 18:46:54 +0000 Subject: [PATCH] Don't set lo_name and clobber lo_flags in lock_profile_object_init(). This was just wasteful when this was always called before lock_init() (which overwrote both fields each time), but when lock_profile_object_init() was moved into lock_init() the clearing of lo_flags proved fatal (all locks became spin locks to _sleep(), etc.) Reported by: kris --- sys/sys/lock_profile.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/sys/sys/lock_profile.h b/sys/sys/lock_profile.h index 26ee57cc6ca..18c21b7a791 100644 --- a/sys/sys/lock_profile.h +++ b/sys/sys/lock_profile.h @@ -84,8 +84,6 @@ static inline void lock_profile_object_init(struct lock_object *lo, struct lock_ u_int hash = 0; struct lock_profile_object *l = &lo->lo_profile_obj; - lo->lo_flags = 0; - lo->lo_name = name; l->lpo_acqtime = 0; l->lpo_waittime = 0; l->lpo_filename = NULL;