From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Lennert Van Alboom <lennert.vanalboom@ugent.be>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: possible memleak in 2.6.11-rc1
Date: Fri, 21 Jan 2005 09:49:07 +0100 [thread overview]
Message-ID: <20050121084906.GF2763@suse.de> (raw)
In-Reply-To: <20050120191943.0ac5bad5.akpm@osdl.org>
On Thu, Jan 20 2005, Andrew Morton wrote:
> Lennert Van Alboom <lennert.vanalboom@ugent.be> wrote:
> >
> > Possible memleak in 2.6.11-rc1?
>
> Please wait for it to happen again and then send the contents of
> /proc/meminfo and /proc/slabinfo.
I've seen the same thing btw, after 2 days on 2.6.11-rc1 most of memory
is gone. There definitely seems to be a leak in 2.6.11-rc1 that wasn't
there in 2.6.10.
I'll try and save the meminfo/slabinfo as well.
--
Jens Axboe
prev parent reply other threads:[~2005-01-21 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 18:56 PROBLEM: possible memleak in 2.6.11-rc1 Lennert Van Alboom
2005-01-21 3:19 ` Andrew Morton
2005-01-21 8:49 ` Jens Axboe [this message]
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=20050121084906.GF2763@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=lennert.vanalboom@ugent.be \
--cc=linux-kernel@vger.kernel.org \
/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.