public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pedro Venda <pjvenda@arrakis.dhis.org>
To: Pedro Venda <pjvenda@arrakis.dhis.org>
Cc: Noel Maddy <noel@zhtwn.com>,
	Parag Warudkar <kernel-stuff@comcast.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible leak in kernel 2.6.10-ac12
Date: Thu, 17 Feb 2005 02:44:03 +0000	[thread overview]
Message-ID: <421404F3.5030502@arrakis.dhis.org> (raw)
In-Reply-To: <4213EA7F.4070107@arrakis.dhis.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pedro Venda wrote:
| Noel Maddy wrote:
| | On Thu, Feb 17, 2005 at 12:02:33AM +0000, Pedro Venda wrote:
| |
| |
| |>admin proc # cat slabinfo
| |
| | ...
| |
| |>biovec-1           74224  74354     16  226    1 : tunables  120
| 60    0 :
| slabdata    329    329      0
| |>bio                74212  74237     64   61    1 : tunables  120
| 60    0 :
| slabdata   1217   1217      0
| |
| |
| | If you're using md, you need this patch to fix a bio leak:
| |
| | http://linux.bkbits.net:8080/linux-2.6/diffs/drivers/md/md.c@1.234
|
| thanks.
|
| has this patch been included in the recent rc's?
|
| and howcome the other servers work normally [all with md]? at least so
| far the
| memory usages aren't concerning, although the linear increase is
| starting to
| show. perhaps the [different] apps running on them don't expose the leak
| as well
| the one that broke today... is that reasonable?

correction: after looking at /proc/slabinfo, the counters around the bio lines
are 10-100 times bigger than all the other, so their also leaking.

I read some discussion on this list around this issue and people were not
positive the leak came from md...

any comments?

regards.
- --

Pedro João Lopes Venda
email: pjvenda@arrakis.dhis.org
http://arrakis.dhis.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCFATzeRy7HWZxjWERApHtAKDsX1UVnKP1JICe1/RrzuzF00P84QCfac4+
Mtxq0Y31MFhdsIgBf5S0n/Y=
=u/li
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-02-17  2:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16 23:28 possible leak in kernel 2.6.10-ac12 Pedro Venda
2005-02-16 23:35 ` Parag Warudkar
2005-02-17  0:02   ` Pedro Venda
2005-02-17  0:38     ` Noel Maddy
2005-02-17  0:51       ` Pedro Venda
2005-02-17  2:44         ` Pedro Venda [this message]
2005-02-17 23:14   ` Bill Davidsen
2005-02-19 12:37   ` Pedro Venda
2005-02-19 14:48     ` Parag Warudkar
2005-02-17  9:29 ` Maciej Soltysiak

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=421404F3.5030502@arrakis.dhis.org \
    --to=pjvenda@arrakis.dhis.org \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noel@zhtwn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox