Message-ID: <1353885594.22969.34.camel@soupermouf>
Subject: Re: kmemleak failure (was Re: backing up ext4 fs, system
 unresponsive, thrashing like crazy even though swap is unused)
From: Dimitrios Apostolou <jimis@gmx.net>
To: linux-kernel@vger.kernel.org
Date: Mon, 26 Nov 2012 01:19:54 +0200
In-Reply-To: <1353883315.22969.31.camel@soupermouf>
References: <1353851735.22969.18.camel@soupermouf>
	 <1353871800.22969.28.camel@soupermouf>
	 <1353883315.22969.31.camel@soupermouf>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 895
Lines: 21

On Mon, 2012-11-26 at 00:41 +0200, Dimitrios Apostolou wrote:
> Hello,
> 
> I tried running a kmemleak and DEBUG_SLUB enabled kernel, but almost
> within 5 minutes of starting the backup process, I got:
> 
> [  486.863124] kmemleak: Cannot allocate a kmemleak_object structure
> [  486.887195] kmemleak: Automatic memory scanning thread ended
> [  486.906604] kmemleak: Kernel memory leak detector disabled

Important detail: I decided to try kmemleak after suspecting a leak
because 'echo 3>/proc/sys/vm/drop_caches' left about 90MB out of 118MB
of ext4_inode_cache, and I found no way to get rid of that (via
remounting filesystems for example).


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/