From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: akpm@osdl.org, linus@osdl.org, anton@samba.org, paulus@samba.org,
axboe@suse.de, piggin@cyberone.com.au,
viro@parcelfarce.linux.theplanet.co.uk, hch@lst.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iSeries virtual disk
Date: Thu, 26 Feb 2004 20:50:17 -0500 [thread overview]
Message-ID: <403EA259.5050105@pobox.com> (raw)
In-Reply-To: <20040227114240.6e26d870.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> On Thu, 26 Feb 2004 02:29:26 -0500 Jeff Garzik <jgarzik@pobox.com> wrote:
>>2) num_req_outstanding accessed without lock in do_viodasd_request
>>(driver's request_fn). all other accesses are inside spinlock.
>
>
> This is actually OK because:
> 1) if we see a value too large, when it get decremented by
> handle_read_write, all the queue requst functions will get rerun.
> 2) in send_request, if we get an error and decrement the count
> to zero, then the count could have been at most 1 (sonce sends
> are serialised) so in the request funtion, we would not have
> stopped processing requests.
That doesn't solve the race though... IMO protect it with the spinlock
and be done with it...
>>5) is it really OK to call viodasd_open() and viodasd_release() multiple
>>times? These functions do not look guarded against multiple openers.
>
>
> It is OK.
I need more explanation than that.
Multiple openers _are_ supported at the block layer, and this driver
does not guard against multiple openers.
Thanks,
Jeff
next prev parent reply other threads:[~2004-02-27 1:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040123163504.36582570.sfr@canb.auug.org.au>
[not found] ` <20040122221136.174550c3.akpm@osdl.org>
2004-02-26 6:23 ` [PATCH] iSeries virtual disk Stephen Rothwell
2004-02-26 7:29 ` Jeff Garzik
2004-02-26 7:40 ` Jens Axboe
2004-02-27 0:44 ` Stephen Rothwell
2004-02-26 7:52 ` Stephen Rothwell
2004-02-26 7:58 ` Jeff Garzik
2004-02-27 0:42 ` Stephen Rothwell
2004-02-27 1:50 ` Jeff Garzik [this message]
2004-02-27 2:45 ` Stephen Rothwell
2004-02-27 2:50 ` Jeff Garzik
2004-02-26 9:51 ` Christoph Hellwig
2004-02-27 1:04 ` Stephen Rothwell
2004-02-27 11:32 ` Christoph Hellwig
2004-02-27 11:57 ` Stephen Rothwell
2004-02-27 12:13 ` Christoph Hellwig
2004-02-27 13:26 ` Stephen Rothwell
2004-02-27 13:37 ` Christoph Hellwig
2004-02-27 13:44 ` Christoph Hellwig
2004-02-27 23:26 ` Stephen Rothwell
2004-02-26 17:35 ` Linus Torvalds
2004-02-27 0:45 ` Stephen Rothwell
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=403EA259.5050105@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=axboe@suse.de \
--cc=hch@lst.de \
--cc=linus@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=piggin@cyberone.com.au \
--cc=sfr@canb.auug.org.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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