From: Theodore Tso <tytso@mit.edu>
To: Quentin Godfroy <godfroy@clipper.ens.fr>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: possible (ext4 related?) memory leak in kernel 2.6.26
Date: Wed, 8 Oct 2008 22:38:37 -0400 [thread overview]
Message-ID: <20081009023837.GC17512@mit.edu> (raw)
In-Reply-To: <200810082355.m98NtZkQ012577@goelette.ens.fr>
On Thu, Oct 09, 2008 at 01:52:46AM +0200, Quentin Godfroy wrote:
>
> Indeed after a couple of days of uptime the number of dirty blocks do not go
> further than ~50, so I think the bug is corrected as far as I am concerned.
>
> By the way, why does the kernel not commit to memory these remaining buffers
> when the memory is scarse (say instead of firing an OOM killer)?
The bug was the jbd2 code was bumping the reference count for the
buffers, so they were considered "in-use" and thus couldn't be freed
and released for other uses.
Regards,
- Ted
next prev parent reply other threads:[~2008-10-09 2:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 20:27 possible (ext4 related?) memory leak in kernel 2.6.26 Quentin Godfroy
2008-09-30 21:18 ` Theodore Tso
2008-09-30 22:23 ` Quentin
2008-10-03 0:35 ` Theodore Tso
2008-10-05 9:15 ` Quentin Godfroy
2008-10-05 12:27 ` Theodore Tso
2008-10-05 16:12 ` Quentin Godfroy
2008-10-06 2:50 ` Theodore Tso
2008-10-06 15:30 ` Eric Sandeen
2008-10-06 15:50 ` Renato S. Yamane
2008-10-06 17:55 ` Theodore Tso
2008-10-07 22:12 ` Theodore Tso
2008-10-08 0:02 ` Quentin Godfroy
2008-10-08 0:53 ` Theodore Tso
2008-10-08 23:52 ` Quentin Godfroy
2008-10-09 2:38 ` Theodore Tso [this message]
2008-10-02 18:36 ` Aneesh Kumar K.V
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=20081009023837.GC17512@mit.edu \
--to=tytso@mit.edu \
--cc=godfroy@clipper.ens.fr \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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.