From 8fa36d412722ef0861e6cfdba0ddf4f31d1f9a71 Mon Sep 17 00:00:00 2001
From: Manjunathappa Prakash <prakashpm@codeaurora.org>
Date: Fri, 10 Nov 2017 20:41:09 -0800
Subject: [PATCH] qcacmn: skb memory leak, log skb being leaked

Log skb address being leaked, it will help to identify the
state of skb during memory leak.
For example if it was dma mapped, by looking at skb->cb fields

Change-Id: I09e9aa9f69ef6b24e709bfbd25c12ac00ab1167c
CRs-Fixed: 2142469
---
 qdf/linux/src/qdf_nbuf.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/qdf/linux/src/qdf_nbuf.c b/qdf/linux/src/qdf_nbuf.c
index ef168cd147f4..e28e72bcd780 100644
--- a/qdf/linux/src/qdf_nbuf.c
+++ b/qdf/linux/src/qdf_nbuf.c
@@ -1627,9 +1627,9 @@ void qdf_net_buf_debug_exit(void)
 			p_prev = p_node;
 			p_node = p_node->p_next;
 			count++;
-			qdf_print("SKB buf memory Leak@ File %s, @Line %d, size %zu\n",
+			qdf_print("SKB buf memory Leak@ File %s, @Line %d, size %zu, nbuf %pK\n",
 				  p_prev->file_name, p_prev->line_num,
-				  p_prev->size);
+				  p_prev->size, p_prev->net_buf);
 			qdf_nbuf_track_free(p_prev);
 		}
 		spin_unlock_irqrestore(&g_qdf_net_buf_track_lock[i], irq_flag);