From: James Bottomley <James.Bottomley@SteelEye.com>
To: Hannes Reinecke <hare@suse.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix reference counting for failed SCSI devices
Date: Wed, 25 May 2005 07:27:23 -0500 [thread overview]
Message-ID: <1117024043.5071.6.camel@mulgrave> (raw)
In-Reply-To: <4294201D.4070304@suse.de>
On Wed, 2005-05-25 at 08:50 +0200, Hannes Reinecke wrote:
> >>+ class_device_put(&sdev->sdev_classdev);
> >
> > This is unnecessary since the class device is simply occupying a private
> > area in the scsi_device. As long as its never made visible to the
> > system, its refcount is irrelevant
> >
> It's not. Whenever you try to rmmod the adapter it becomes highly
> relevant. If it doesn't crash you've at least generated a memleak as the
> class device is never freed.
> (And these are quite a few for Wide-SCSI Double-channel adapters ...)
? Look at the code; you're not doing a put on a pointer to the
sdev_classdev, you're doing a put on a reference to it.
It's defined in scsi_device.h:
struct scsi_device {
...
struct class_device sdev_classdev;
...
};
so it's contained within the scsi_device. Freeing the scsi_device frees
the classdev (and the gendev).
James
next prev parent reply other threads:[~2005-05-25 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 9:38 [PATCH] Fix reference counting for failed SCSI devices Hannes Reinecke
2005-05-24 22:57 ` James Bottomley
2005-05-25 6:50 ` Hannes Reinecke
2005-05-25 12:27 ` James Bottomley [this message]
2005-05-25 12:46 ` Hannes Reinecke
2005-05-25 14:58 ` James Bottomley
2005-05-25 15:16 ` Hannes Reinecke
2005-05-25 17:51 ` James Bottomley
2005-05-25 18:01 ` Matthew Wilcox
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=1117024043.5071.6.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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