From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754032AbZIKJ3e (ORCPT ); Fri, 11 Sep 2009 05:29:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751728AbZIKJ3d (ORCPT ); Fri, 11 Sep 2009 05:29:33 -0400 Received: from cam-admin0.cambridge.arm.com ([193.131.176.58]:47577 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751150AbZIKJ3d (ORCPT ); Fri, 11 Sep 2009 05:29:33 -0400 To: Tetsuo Handa Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org Subject: Re: [2.6.31] Memory leak in load_module()? References: <200909111638.IDC17135.FOHJOtFFMQSVLO@I-love.SAKURA.ne.jp> From: Catalin Marinas Date: Fri, 11 Sep 2009 10:29:25 +0100 In-Reply-To: <200909111638.IDC17135.FOHJOtFFMQSVLO@I-love.SAKURA.ne.jp> (Tetsuo Handa's message of "Fri\, 11 Sep 2009 16\:38\:46 +0900") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 11 Sep 2009 09:29:26.0761 (UTC) FILETIME=[5B23FD90:01CA32C2] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tetsuo Handa wrote: > I changed CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE to 2000 and did > > # insmod /lib/modules/2.6.31/kernel/drivers/edac/r82600_edac.ko > insmod: error inserting '/lib/modules/2.6.31/kernel/drivers/edac/r82600_edac.ko': -1 Unknown symbol in module > # echo scan > /sys/kernel/debug/kmemleak > # dmesg > r82600_edac: Unknown symbol edac_mc_del_mc > r82600_edac: Unknown symbol edac_mc_add_mc > r82600_edac: Unknown symbol edac_pci_create_generic_ctl > r82600_edac: Unknown symbol edac_mc_alloc > r82600_edac: Unknown symbol edac_mc_find_csrow_by_page > r82600_edac: Unknown symbol edac_mc_free > r82600_edac: Unknown symbol edac_mc_handle_ce > r82600_edac: Unknown symbol edac_mc_handle_ue > r82600_edac: Unknown symbol edac_pci_release_generic_ctl > kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) > # tail -n 4 /sys/kernel/debug/kmemleak > unreferenced object 0xd643a788 (size 32): > comm "insmod", pid 2854, jiffies 4294791099 > backtrace: > [] 0xffffffff > > Is this real memory leak? It could be but isn't stack tracing enabled on your system? The backtrace doesn't seem very useful. -- Catalin