From: Erik Hensema <erik@hensema.net>
To: "David S. Miller" <davem@redhat.com>
Cc: torvalds@osdl.org, netdev@oss.sgi.com, acme@conectiva.com.br
Subject: Re: 2.6.0: something is leaking memory
Date: Tue, 6 Jan 2004 20:36:15 +0100 [thread overview]
Message-ID: <20040106193615.GA4544@bender.home.hensema.net> (raw)
In-Reply-To: <20040106095909.7243b2ce.davem@redhat.com>
On Tue, Jan 06, 2004 at 09:59:09AM -0800, David S. Miller wrote:
> On Tue, 6 Jan 2004 16:59:34 +0100
> Erik Hensema <erik@hensema.net> wrote:
>
> > David: are you sure it was fixed in rc1?
> >
> > It doesn't seem to be in -rc2 either.
> >
> > This is after 26 hours uptime:
> >
> > tcp6_sock 6246 6248 1024 4 1 : tunables 54 27 0
> > : slabdata 1562 1562 0
>
> Someone mentioned about a bug in the userland program you're
> using that is openning these sockets? Something about leaving sockets
> not closed.
That's correct. I suspect that this exposes the leak in the kernel more
promimently than on other systems.
The leak is in nscd, it doesn't properly close sockets to my LDAP server.
This is not a kernel problem I think, because it also leaks in 2.4.x. The
kernelspace leak however is not in 2.4, only in 2.6.
I'm restarting nscd in cron every night, which makes the CLOSE_WAIT sockets
go away. However the kernel resources are not freed it seems.
--
Erik Hensema (erik@hensema.net)
next prev parent reply other threads:[~2004-01-06 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <slrnbvgohn.1pb.erik@dexter.hensema.net>
[not found] ` <Pine.LNX.4.58.0401041257290.2162@home.osdl.org>
[not found] ` <slrnbvh1hd.jl6.erik@dexter.hensema.net>
2004-01-05 2:30 ` 2.6.0: something is leaking memory Linus Torvalds
2004-01-05 4:48 ` David S. Miller
2004-01-05 18:14 ` Erik Hensema
2004-01-06 15:59 ` Erik Hensema
2004-01-06 17:59 ` David S. Miller
2004-01-06 19:03 ` Arnaldo Carvalho de Melo
2004-01-06 19:36 ` Erik Hensema [this message]
2004-01-05 4:52 ` (usagi-core 16947) " YOSHIFUJI Hideaki / 吉藤英明
2004-03-29 15:43 ` YOSHIFUJI Hideaki / 吉藤英明
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=20040106193615.GA4544@bender.home.hensema.net \
--to=erik@hensema.net \
--cc=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).