From: Steven Whitehouse <steve@gw.chygwyn.com>
To: davej@suse.de (Dave Jones)
Cc: stelian.pop@fr.alcove.com (Stelian Pop),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
pavel@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 2.5.8-pre1] nbd compile fixes...
Date: Thu, 4 Apr 2002 15:12:27 +0100 (BST) [thread overview]
Message-ID: <200204041412.PAA17697@gw.chygwyn.com> (raw)
In-Reply-To: <20020404162844.Z20040@suse.de> from "Dave Jones" at Apr 04, 2002 04:28:44 PM
Hi,
>
> On Thu, Apr 04, 2002 at 02:50:25PM +0100, Steven Whitehouse wrote:
> > > 2.4 simply does a s/queue_lock/tx_lock/ on drivers/block/nbd.c
> > > I'll push that to Linus later today
> > Not quite. They cover different things. The queue_lock originally covered the
> > queue and the request sending function. There was an obscure deadlock which
> > could occur in this case hence the split to a spin lock to cover the queue
> > and a semaphore to cover only the request sending function (hence tx_lock
> > rather than queue lock).
>
> *nod* I wussed out and just took the easy bits when I forward ported
> those changes from 2.4
> http://www.codemonkey.org.uk/linux-2.5_drivers_block_nbd.c.diff
>
> I dropped the actual fix because it was incompatible with the bio
> changes iirc.
>
That was my conclusion too. Since its now possible to mark requests
REQ_STARTED my current 2.5 patch does that (and leaves requests on the
request queue) rather than maintaining a separate internal queue like the
2.4 version does, but its fairly similar other than that.
> > I've got a 2.5 version of that patch on my patches page at the moment, but
> > due to the block layer changes (if I've understood them correctly) the
> > fix should be done in a slightly different way. The reason that I've not
> > submitted the patch for 2.5 is that it doesn't yet work and I've not had
> > a chance to investigate properly yet (it hangs on writes sometimes). I'm
> > sure its probably something silly that I've done but I just don't see it
> > at the moment. Any hints or clues are welcome :-)
>
> URL ?
>
Sorry, I should have mentioned that earlier:
http://www.chygwyn.com/~steve/kpatch/nbd-2.5.7-deadlock.diff
Steve.
prev parent reply other threads:[~2002-04-04 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 13:58 Stelian Pop
2002-04-04 14:02 ` Dave Jones
2002-04-04 13:50 ` Steven Whitehouse
2002-04-04 14:28 ` Dave Jones
2002-04-04 14:12 ` Steven Whitehouse [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=200204041412.PAA17697@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@atrey.karlin.mff.cuni.cz \
--cc=stelian.pop@fr.alcove.com \
/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
all inboxes | Powered by JetHome®