From ee8f6257666273c9647fda39cd2c6b63a28a9a38 Mon Sep 17 00:00:00 2001 From: Dustin Brown Date: Thu, 2 Aug 2018 10:57:58 -0700 Subject: [PATCH] qcacmn: Clarify memory domain mismatch log The current diagnostic message that gets printed in the event some memory is freed in a different memory domain than it was allocated from is confusing. Rather than using "found" and "expected," use "allocated" and "current" to differentiate the different memory domains. Change-Id: I45efeb892d2c75a3f0b13d41e43b421a2b1a139e CRs-Fixed: 2290148 --- qdf/linux/src/qdf_mem.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/qdf/linux/src/qdf_mem.c b/qdf/linux/src/qdf_mem.c index 37452a9dcb72..718d50df0fcd 100644 --- a/qdf/linux/src/qdf_mem.c +++ b/qdf/linux/src/qdf_mem.c @@ -269,12 +269,11 @@ qdf_mem_header_assert_valid(struct qdf_mem_header *header, qdf_err("Corrupted memory domain 0x%x", header->domain); if (error_bitmap & QDF_MEM_WRONG_DOMAIN) - qdf_err("Memory domain mismatch; found %s(%d), expected %s(%d)", + qdf_err("Memory domain mismatch; allocated:%s(%d), current:%s(%d)", qdf_debug_domain_name(header->domain), header->domain, qdf_debug_domain_name(current_domain), current_domain); - panic("A fatal memory error was detected @ %s:%d", - file, line); + QDF_DEBUG_PANIC("Fatal memory error detected @ %s:%d", file, line); } #endif /* MEMORY_DEBUG */