[Xen-changelog] [xen staging] xen: make CONFIG_DEBUG_LOCKS usable without CONFIG_DEBUG

[patchbot@xxxxxxx]

commit e8660f82c9731d3ab913b58a2304eef09461f2c3
Author:     Juergen Gross <jgross@xxxxxxxx>
AuthorDate: Tue Jan 21 11:13:01 2020 +0100
Commit:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
CommitDate: Fri Jan 24 15:16:23 2020 +0000

    xen: make CONFIG_DEBUG_LOCKS usable without CONFIG_DEBUG
    
    In expert mode it is possible to enable CONFIG_DEBUG_LOCKS without
    having enabled CONFIG_DEBUG. The coding is depending on CONFIG_DEBUG
    as it is using ASSERT(), however.
    
    Fix that by using BUG_ON() instead of ASSERT() in rel_lock().
    
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
---
 xen/common/spinlock.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xen/common/spinlock.c b/xen/common/spinlock.c
index 286f916bca..344981c54a 100644
--- a/xen/common/spinlock.c
+++ b/xen/common/spinlock.c
@@ -86,7 +86,7 @@ static void got_lock(union lock_debug *debug)
 static void rel_lock(union lock_debug *debug)
 {
     if ( atomic_read(&spin_debug) > 0 )
-        ASSERT(debug->cpu == smp_processor_id());
+        BUG_ON(debug->cpu != smp_processor_id());
     debug->cpu = SPINLOCK_NO_CPU;
 }
 
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog