From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: kmemleak report in 3.9.5 related to ext4_alloc_inode Date: Tue, 11 Jun 2013 11:24:31 -0700 Message-ID: <51B76B5F.1090301@candelatech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: linux-ext4@vger.kernel.org Return-path: Received: from mail.candelatech.com ([208.74.158.172]:42131 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755957Ab3FKSYc (ORCPT ); Tue, 11 Jun 2013 14:24:32 -0400 Received: from [192.168.100.226] (firewall.candelatech.com [70.89.124.249]) (authenticated bits=0) by ns3.lanforge.com (8.14.2/8.14.2) with ESMTP id r5BIOVBp020948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Jun 2013 11:24:31 -0700 Sender: linux-ext4-owner@vger.kernel.org List-ID: Hello! I see this kmemleak report in a slightly modified 3.9.5 kernel (no patches to the ext4 subsystem). Any idea if this is real and/or what a fix would be? unreferenced object 0xffff8801170bb700 (size 40): comm "prelink", pid 25152, jiffies 4352882167 (age 29213.208s) hex dump (first 32 bytes): 80 cb 94 15 01 88 ff ff d0 4f 4d 18 01 88 ff ff .........OM..... 01 00 00 00 00 00 00 00 40 4d 3a 18 01 88 ff ff ........@M:..... backtrace: [] kmemleak_alloc+0x73/0x98 [] slab_post_alloc_hook+0x28/0x2a [] kmem_cache_alloc+0xb2/0x123 [] __debug_object_init+0x43/0x35f [] debug_object_init+0x14/0x16 [] __init_work+0x27/0x29 [] ext4_alloc_inode+0x173/0x1cb [] alloc_inode+0x1d/0x78 [] iget_locked+0x6d/0x12f [] ext4_iget+0x2c/0x932 [] ext4_lookup+0xd2/0x12a [] lookup_real+0x2c/0x47 [] __lookup_hash+0x33/0x3c [] walk_component+0x73/0x171 [] path_lookupat+0xa7/0x304 [] filename_lookup+0x2b/0x82 Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com