From: Matthew Wilcox <willy@debian.org>
To: Brian King <brking@us.ibm.com>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_remove_device locking
Date: Fri, 2 Jul 2004 21:23:51 +0100 [thread overview]
Message-ID: <20040702202351.GP30334@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <40E5C32A.3060002@us.ibm.com>
On Fri, Jul 02, 2004 at 03:18:50PM -0500, Brian King wrote:
> {
> - if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
> + struct Scsi_Host *shost = sdev->host;
> + down(&shost->scan_mutex);
> +
> + if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0) {
> + up(&shost->scan_mutex);
> return;
> + }
>
> class_device_unregister(&sdev->sdev_classdev);
> if (sdev->transport_classdev.class)
> @@ -537,6 +542,7 @@ void scsi_remove_device(struct scsi_devi
> if (sdev->host->transportt->cleanup)
> sdev->host->transportt->cleanup(sdev);
> put_device(&sdev->sdev_gendev);
> + up(&shost->scan_mutex);
> }
IMO, this would be better done as:
{
struct Scsi_Host *shost = sdev->host;
down(&shost->scan_mutex);
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
goto out;
...
out:
up(&shost->scan_mutex);
}
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-07-02 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 23:29 scsi_add_device/scsi_remove_device oops Brian King
2004-07-02 20:18 ` [PATCH] scsi_remove_device locking Brian King
2004-07-02 20:23 ` Matthew Wilcox [this message]
2004-07-02 20:34 ` 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=20040702202351.GP30334@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=James.Bottomley@steeleye.com \
--cc=brking@us.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