public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Noel Maddy <noel@zhtwn.com>
To: Pedro Venda <pjvenda@arrakis.dhis.org>
Cc: Parag Warudkar <kernel-stuff@comcast.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: possible leak in kernel 2.6.10-ac12
Date: Wed, 16 Feb 2005 19:38:46 -0500	[thread overview]
Message-ID: <20050217003846.GA5615@uglybox.localnet> (raw)
In-Reply-To: <4213DF19.10209@arrakis.dhis.org>

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


Index: ac-dev/drivers/md/md.c
===================================================================
--- ac-dev.orig/drivers/md/md.c	2005-02-07 17:50:37.000000000 -0500
+++ ac-dev/drivers/md/md.c	2005-02-08 17:49:57.000000000 -0500
@@ -336,8 +336,6 @@
 	struct completion event;
 	int ret;
 
-	bio_get(bio);
-
 	rw |= (1 << BIO_RW_SYNC);
 
 	bio->bi_bdev = bdev;
-- 
It's a big galaxy, Mr. Scott.
						    -- Lieutenant Uhura
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Noel Maddy <noel@zhtwn.com>

  reply	other threads:[~2005-02-17  0:38 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 [this message]
2005-02-17  0:51       ` Pedro Venda
2005-02-17  2:44         ` Pedro Venda
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=20050217003846.GA5615@uglybox.localnet \
    --to=noel@zhtwn.com \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjvenda@arrakis.dhis.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