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
Cette révision appartient à :
Dustin Brown
2018-08-02 10:57:58 -07:00
révisé par nshrivas
Parent 95fc62f8fc
révision ee8f625766

Voir le fichier

@@ -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 */