From: Elias Oltmanns <eo@nebensachen.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI: Fix some locking issues
Date: Thu, 03 Jul 2008 09:25:35 +0200 [thread overview]
Message-ID: <87skur1lao.fsf@denkblock.local> (raw)
In-Reply-To: 1215016350.3330.32.camel@localhost.localdomain
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Wed, 2008-07-02 at 17:59 +0200, Elias Oltmanns wrote:
>> James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
[...]
>> > unless we get down to zero depth in which case the decrements are done
>> > under lock.
>>
>> Sorry, but this simply doesn't resolve the matter at hand.
>> scsi_finish_command() can change (host|device)_blocked values to zero at
>> any time currently *not* protected by any lock. In much the same way
>> scsi_queue_insert() can change these values from zero to something else
>> at any time.
>
> Look more closely at the requirements for the decrements: There have to
> be no outstanding commands: nothing can be in scsi_finish_command for
> the device (or the host for host_blocked).
Yes, I agree as far as the decrements are concerned. There still is the
check
if (sdev->device_blocked)
which can happen while ->device_blocked is changed either by
scsi_finish_command() or scsi_queue_insert(). If I understand Matthew and
you correctly, this doesn't pose any problem because assigning an int is
an atomic operation anyway.
Thanks for explaining,
Elias
prev parent reply other threads:[~2008-07-03 7:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 11:38 [PATCH] SCSI: Fix some locking issues Elias Oltmanns
2008-07-01 21:37 ` Elias Oltmanns
2008-07-02 1:55 ` James Bottomley
2008-07-02 7:08 ` Elias Oltmanns
2008-07-02 11:50 ` Jens Axboe
2008-07-02 14:49 ` James Bottomley
2008-07-02 18:45 ` Jens Axboe
2008-07-02 20:18 ` James Bottomley
2008-07-03 7:53 ` Elias Oltmanns
2008-07-03 10:38 ` Elias Oltmanns
2008-07-03 11:24 ` Jens Axboe
2008-07-03 16:31 ` James Bottomley
2008-07-03 17:54 ` Jens Axboe
2008-07-03 19:47 ` Elias Oltmanns
2008-07-03 21:33 ` James Bottomley
2008-07-02 14:46 ` James Bottomley
2008-07-02 15:59 ` Elias Oltmanns
2008-07-02 16:23 ` Matthew Wilcox
2008-07-03 7:12 ` Elias Oltmanns
2008-07-03 15:22 ` James Bottomley
2008-07-03 19:39 ` Elias Oltmanns
2008-07-03 15:47 ` Matthew Wilcox
2008-07-02 16:32 ` James Bottomley
2008-07-03 7:25 ` Elias Oltmanns [this message]
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=87skur1lao.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=James.Bottomley@HansenPartnership.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.