public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: linux-2.6.0-test11 [BUG] -- scsi_add/remove_device - out of memory
Date: Wed, 10 Dec 2003 14:02:23 +0000	[thread overview]
Message-ID: <20031210140223.A1832@infradead.org> (raw)
In-Reply-To: <200312101012.17027.heiko.carstens@de.ibm.com>; from heiko.carstens@de.ibm.com on Wed, Dec 10, 2003 at 10:12:17AM +0100

On Wed, Dec 10, 2003 at 10:12:17AM +0100, Heiko Carstens wrote:
> Hello all,
> 
> it looks to me as if the SCSI stack has a memory leak. If I have the following
> endless loop in our ZFCP LLD we end up within a very short time in an out
> of memory situation (tested on an S390 virtual machine with 128MB):
> 
> while(1) {
>         scsi_add_device(...)
>         scsi_remove_device(...);
> }
> 
> It takes only about 40 iterations to reach the out of memory situation.
> The device that gets added and removed does respond to Inquiry commands.
> Since I'm not sure what are the pending fixes for the SCSI stack I'm wondering
> if this is a known bug.

Sounds there's a scsi_device_put missing somewherein your driver..


  reply	other threads:[~2003-12-10 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10  9:12 linux-2.6.0-test11 [BUG] -- scsi_add/remove_device - out of memory Heiko Carstens
2003-12-10 14:02 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-10 14:18 Heiko Carstens
     [not found] <OFE5F05878.12C1E995-ONC1256DF8.004D7413-C1256DF8.004E538F@de.ibm.com>
2003-12-10 15:09 ` Christoph Hellwig
2004-01-13  9:44 Heiko Carstens
2004-01-13 16:26 ` Mike Anderson
2004-01-13 18:11   ` Mike Anderson
2004-01-14 10:39 Heiko Carstens

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=20031210140223.A1832@infradead.org \
    --to=hch@infradead.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-scsi@vger.kernel.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