netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Hensema <erik@hensema.net>
To: "David S. Miller" <davem@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, netdev@oss.sgi.com
Subject: Re: 2.6.0: something is leaking memory
Date: Tue, 6 Jan 2004 16:59:34 +0100	[thread overview]
Message-ID: <20040106155933.GA3373@bender.home.hensema.net> (raw)
In-Reply-To: <20040104204834.40b6ca51.davem@redhat.com>

On Sun, Jan 04, 2004 at 08:48:34PM -0800, David S. Miller wrote:
> On Sun, 4 Jan 2004 18:30:21 -0800 (PST)
> Linus Torvalds <torvalds@osdl.org> wrote:
> 
> > You've got 19 _megabytes_ allocated to "tcp6_sock", and they are all 
> > marked as "active". That's almost certainly the leaking bug.
> > 
> > Everything else looks reasonably normal.
>  ...
> > David?
> 
> Fixed by changeset 1.1496.16.1 which is in 2.6.1-rc1

The leak seems to be in 2.6.1-rc1 too and I can't find any IPv6 related
fixes wrt memory in the long format changelog of 2.6.1-rc1.

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


-- 
Erik Hensema (erik@hensema.net)

  parent reply	other threads:[~2004-01-06 15:59 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 [this message]
2004-01-06 17:59           ` David S. Miller
2004-01-06 19:03             ` Arnaldo Carvalho de Melo
2004-01-06 19:36             ` Erik Hensema
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=20040106155933.GA3373@bender.home.hensema.net \
    --to=erik@hensema.net \
    --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).