From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com, thomas@habets.pp.se
Subject: Re: Fw: PROBLEM: Memory leak in -test9?
Date: Tue, 11 Nov 2003 13:06:15 -0800 [thread overview]
Message-ID: <20031111130615.23006c98.akpm@osdl.org> (raw)
In-Reply-To: <20031111130513.67caea63.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
>
> A memory leak in the tcp6_sock slab.
>
Begin forwarded message:
Date: Tue, 11 Nov 2003 18:27:12 +0100
From: Thomas Habets <thomas@habets.pp.se>
To: Jörn Engel <joern@wohnheim.fh-wedel.de>
Cc: Henrik Storner <henrik@hswn.dk>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Memory leak in -test9?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 11 November 2003 17:27, Jörn Engel wrote:
> Looks familiar. Can you recreate and send the output from
> /proc/slabinfo?
Oh, I didn't notice that file. :-)
Recreating is just booting and waiting for a week, but the box is still up.
This is the line that stands out (complete file attached, 137 lines).
tcp6_sock 111663 111664 960 4 1 : tunables 54 27 0 :
slabdata 27916 27916 0
I seem to remember a changelog mentioning a leak being fixed in ipv6 code,
but it looks like there may be another one? The only ipv6 service running is
sshd, and the mrtg-sshs that go off every 5 minutes are NOT over ipv6.
netstat -na shows nothing interesting. Only the ssh I connect with uses a bit
of ipv6 (ffff:1.2.3.4). So, one listening socket, and one established.
$ cat /proc/net/sockstat6
TCP6: inuse 2
UDP6: inuse 0
RAW6: inuse 0
FRAG6: inuse 0 memory 0
$ cat /proc/net/rt6_stats
0000 0006 0000 0008 0000 0008 0003
nothing over 6 in /proc/net/dev_snmp6/*
$ cat /proc/net/snmp6
Ip6InReceives 223315
... just 0 ...
Ip6InDelivers 223312
... just 0 ...
Ip6OutRequests 223312
.. nothing that looks interesting ...
- ---------
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "thomas@habets.pp.se" };
char kernel[] = { "Linux 2.4" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt" };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/sRvwKGrpCq1I6FQRAqw1AKDVu+ZEvqwdoFPD18g6Ps1+UG62cACfTatK
pHUgMxWIGHke3USjtUEsKZU=
=/5YW
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-11-11 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 21:05 Fw: PROBLEM: Memory leak in -test9? Andrew Morton
2003-11-11 21:06 ` Andrew Morton [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=20031111130615.23006c98.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
--cc=thomas@habets.pp.se \
/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).