public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [Open/iSCSI] Memory leak in repetitive --login/--logout with v2.0-870.1
Date: Mon, 12 Jan 2009 20:41:13 -0600	[thread overview]
Message-ID: <496BFF49.5030204@cs.wisc.edu> (raw)
In-Reply-To: <496BED4A.7030006@cs.wisc.edu>

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

Mike Christie wrote:
> Nicholas A. Bellinger wrote:
> 
>> Ok, I still have my hands full with LIO v3.0 code atm, so I am not sure
>> how soon I could get to this..
>>
> 
> Don't worry about it. I can replicate it here.
> 

Crazy, I guess it is a leak we always had (at least back to 2.6.22 (did 
not look firther)), and no one noticed. Here is a patch. I will send it 
to James with some other patches I had.

Thanks for the report.

[-- Attachment #2: libiscsi-fix-pool-queue-leak.patch --]
[-- Type: text/plain, Size: 335 bytes --]

diff --git a/drivers/scsi/libiscsi.c b/drivers/scsi/libiscsi.c
index 7225b6e..257c241 100644
--- a/drivers/scsi/libiscsi.c
+++ b/drivers/scsi/libiscsi.c
@@ -1981,6 +1981,7 @@ void iscsi_pool_free(struct iscsi_pool *q)
 		kfree(q->pool[i]);
 	if (q->pool)
 		kfree(q->pool);
+	kfree(q->queue);
 }
 EXPORT_SYMBOL_GPL(iscsi_pool_free);
 

  reply	other threads:[~2009-01-13  2:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 22:22 [Open/iSCSI] Memory leak in repetitive --login/--logout with v2.0-870.1 Nicholas A. Bellinger
2009-01-12  2:02 ` Mike Christie
2009-01-13  0:27   ` Nicholas A. Bellinger
2009-01-13  1:24     ` Mike Christie
2009-01-13  2:41       ` Mike Christie [this message]
2009-01-13 18:32         ` Nicholas A. Bellinger

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=496BFF49.5030204@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=open-iscsi@googlegroups.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