public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: andmike@us.ibm.com
Cc: linux-scsi@vger.kernel.org
Subject: Two questions on scsi_device_{get,put}
Date: Fri, 8 Aug 2003 14:59:56 +0200	[thread overview]
Message-ID: <20030808125956.GA13589@lst.de> (raw)

I'm trying to forward-port my locking infrastructure for
shost->my_devices to the current scsi tree.  As this list is
acquired from irq context we need these locks to be spinlocks,
but for that to work scsi_device_get/scsi_device_put must not
block.

But after your changes it's using the class r/w semaphore for
synchronisation.  What it this protecting except sdev->access_count?
Also what's the reason we can't do the device_del directly but have
to do it in scsi_device_put?

A final nitpick:  you're losing a module refernece for some failure
pathes of scsi_module_get.

             reply	other threads:[~2003-08-08 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 12:59 Christoph Hellwig [this message]
2003-08-11 20:37 ` Two questions on scsi_device_{get,put} Mike Anderson
2003-08-12  8:43   ` Christoph Hellwig

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=20030808125956.GA13589@lst.de \
    --to=hch@lst.de \
    --cc=andmike@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