From: Martin Hicks <mort@bork.org>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: Transport Attributes -- attempt#3
Date: Fri, 16 Jan 2004 11:47:40 -0500 [thread overview]
Message-ID: <20040116164740.GJ27591@localhost> (raw)
In-Reply-To: <OF2D4C46F4.BCE421EB-ONC1256E1C.0045A5CA-C1256E1C.00472906@de.ibm.com>
On Thu, Jan 15, 2004 at 01:52:16PM +0100, Martin Peschke3 wrote:
> Hi,
>
> + if (sdev->transport_classdev.class) {
> + attrs = sdev->host->transportt->attrs;
> + for (i = 0; attrs[i]; i++) {
> + error = class_device_create_file
> (&sdev->transport_classdev,
> + attrs[i]);
> + if (error)
> + scsi_remove_device(sdev);
> + }
> + }
>
> Isn't there a break needed in the error case to quit
> the loop after scsi_remove_device(sdev) in order to
> avoid trouble with sdev in subsequent iterations?
> I am not very familiar with the 2.6 SCSI code. But,
> is scsi_remove_device(sdev) an appropriate answer
> to the failed registration of sysfs attributes?
It looks that way. There are a couple other places in the same function
that need similar fixes.
Thanks
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
next prev parent reply other threads:[~2004-01-16 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 12:52 Transport Attributes -- attempt#3 Martin Peschke3
2004-01-16 16:47 ` Martin Hicks [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 23:20 Martin Peschke3
2004-01-20 23:45 ` Mike Anderson
2004-01-20 12:29 Martin Peschke3
2004-01-07 18:54 Transport Attributes -- attempt#2 Martin Hicks
2004-01-08 13:17 ` Christoph Hellwig
2004-01-14 18:12 ` Transport Attributes -- attempt#3 Martin Hicks
2004-01-14 23:34 ` Andrew Vasquez
2004-01-16 16:40 ` Martin Hicks
2004-01-17 0:23 ` Lincoln Dale
2004-01-14 23:58 ` Patrick Mansfield
2004-01-16 14:54 ` Christoph Hellwig
2004-01-16 16:54 ` Martin Hicks
2004-01-20 0:07 ` Brian King
2004-01-20 19:49 ` Patrick Mansfield
2004-01-20 20:38 ` Brian King
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=20040116164740.GJ27591@localhost \
--to=mort@bork.org \
--cc=MPESCHKE@de.ibm.com \
--cc=hch@infradead.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