Message ID | 20200109134825.31482-3-jgross@suse.com (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | xen: fix CONFIG_DEBUG_LOCKS | expand |
On 09.01.2020 14:48, Juergen Gross wrote: > 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@suse.com> Reviewed-by: Jan Beulich <jbeulich@suse.com>
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; }
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@suse.com> --- xen/common/spinlock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)