From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752741AbbFFOKr (ORCPT ); Sat, 6 Jun 2015 10:10:47 -0400 Received: from mail-pa0-f66.google.com ([209.85.220.66]:33532 "EHLO mail-pa0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751804AbbFFOKi (ORCPT ); Sat, 6 Jun 2015 10:10:38 -0400 From: Masami Ichikawa To: linux-kernel@vger.kernel.org Cc: Masami Ichikawa Subject: [PATCH] kasan: Set shadow memory is not memory leaked Date: Sat, 6 Jun 2015 23:10:31 +0900 Message-Id: <1433599831-6196-1-git-send-email-masami256@gmail.com> X-Mailer: git-send-email 2.4.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org kmemleak reported memory leak in kasan_module_alloc() like following log, even through kasan_free_shadow() frees that address. unreferenced object 0xfffffbfff40ac000 (size 118784): comm "modprobe", pid 196, jiffies 4294878847 (age 87.590s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmemleak_alloc+0x4e/0xc0 [] __vmalloc_node_range+0x340/0x3f0 [] kasan_module_alloc+0x72/0xd0 [] module_alloc+0x78/0xb0 [] module_alloc_update_bounds+0x14/0x70 [] load_module+0xf67/0x4670 [] SyS_init_module+0x1d5/0x220 [] system_call_fastpath+0x12/0x71 [] 0xffffffffffffffff Kmemleak may think anyone take care of result of __vmalloc_node_range() after the function. So, it would be nice to call kmemleak_not_leak() to tell memory is not leaked. Signed-off-by: Masami Ichikawa --- mm/kasan/kasan.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c index 6c513a6..0ef75b9 100644 --- a/mm/kasan/kasan.c +++ b/mm/kasan/kasan.c @@ -430,6 +430,7 @@ int kasan_module_alloc(void *addr, size_t size) __builtin_return_address(0)); if (ret) { + kmemleak_not_leak(ret); find_vm_area(addr)->flags |= VM_KASAN; return 0; } -- 2.4.2