From: Kristof Provost <Kristof@provost-engineering.be>
To: linux-kernel@vger.kernel.org, NeilBrown <neilb@suse.de>,
Jens Axboe <jens.axboe@oracle.com>
Subject: [BUG] memory leak in dm
Date: Tue, 16 Oct 2007 13:38:00 +0200 [thread overview]
Message-ID: <20071016113800.GA4631@luggage> (raw)
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Hi,
I'm seeing a serious memory leak whenever I use my /home partition.
It's an encrypted partition using dm-crypt. Simply running
'stress -d 5' is enough to exhaust the memory in a few minutes.
When I stop 'stress' the memory isn't returned.
This doesn't seem to happen when I run stress on a normal (no dm and
no encryption) partition.
Here's the output of 'free -m' before and after 'stress -d 1 -t 5'
Before:
total used free shared buffers cached
Mem: 751 584 167 0 14 235
-/+ buffers/cache: 334 416
Swap: 980 0 980
After:
total used free shared buffers cached
Mem: 751 619 131 0 12 169
-/+ buffers/cache: 437 313
Swap: 980 0 980
That's 100Mb of RAM gone in 5 seconds.
I'm using a standard x86 centrino laptop.
The log files don't reveal anything suspicious.
git bisect tells me it started in one of these commits:
d24517d793f21edab1a411da95f2c45cb88a84aa,
5bb23a688b2de23d7765a1dd439d89c038378978 and
9cc54d40b8ca01fcefc9151044b6996565061d90.
The bug is still present in the last version of Linus' tree
(65a6ec0d72a07f16719e9b7a96e1c4bae044b591)
Let me know if I can provide more information.
Regards,
Kristof
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-10-16 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 11:38 Kristof Provost [this message]
2007-10-16 11:44 ` [BUG] memory leak in dm Jens Axboe
2007-10-16 13:23 ` Jan-Simon Möller
2007-10-16 15:12 ` Kristof Provost
2007-10-17 8:11 ` Jens Axboe
2007-10-16 12:15 ` Jan-Simon Möller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016113800.GA4631@luggage \
--to=kristof@provost-engineering.be \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.