From: Pavel Machek <pavel@ucw.cz>
To: Lou Langholtz <ldl@aros.net>
Cc: linux-kernel@vger.kernel.org, Steven Whitehouse <steve@chygwyn.com>
Subject: Re: [RFC][PATCH] nbd driver for 2.5.72
Date: Sat, 21 Jun 2003 08:23:06 +0200 [thread overview]
Message-ID: <20030621062306.GA140@elf.ucw.cz> (raw)
In-Reply-To: <3EF3F08B.5060305@aros.net>
Hi!
> The following (attached) patch to the network block device driver (nbd)
> is now specific to just 2.5.72 with various other changes as suggested
> by Pavel and Steven. Please let me know what you think. There's
> definately room for more improvements but I don't believe the existing
> 2.5 series nbd driver (at least up through 2.5.72) works at all. Has
> anyone tested nbd as distributed with 2.5? I've been too busy writing
> this new nbd driver to even have checked the original driver (but some
> of the bugs I've encountered make me believe the original won't work at
> all). Here's a URL to follow to see just the two resultant files (and/or
> the patch in case it doesn't come through as an attachment):
> <http://www.aros.net/~ldl/linux/kernel/2.5.72/>.
>
> Thanks!
>
> PS: Please email me or CC me if you have any feedback for me.
> diff -urN linux-2.5.72/drivers/block/nbd.c linux-2.5.72-new/drivers/block/nbd.c
> --- linux-2.5.72/drivers/block/nbd.c 2003-06-16 22:19:44.000000000 -0600
> +++ linux-2.5.72-new/drivers/block/nbd.c 2003-06-20 21:27:44.650037153 -0600
> @@ -24,10 +25,35 @@
> * 01-3-11 Make nbd work with new Linux block layer code. It now supports
> * plugging like all the other block devices. Also added in MSG_MORE to
> * reduce number of partial TCP segments sent. <steve@chygwyn.com>
> - * 01-12-6 Fix deadlock condition by making queue locks independent of
> + * 01-12-6 Fix deadlock condition by making queue locks independant
of
This actually *introduces* typo.
> #include <asm/uaccess.h>
> #include <asm/types.h>
> +#include <asm/system.h> /* for __xchg()... */
> +#define atomic_exchange(x,ptr,size) __xchg((x),(ptr),(size))
>
atomic_exchange seems to be defined but never used?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-06-21 6:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 5:43 [RFC][PATCH] nbd driver for 2.5.72 Lou Langholtz
2003-06-21 6:23 ` Pavel Machek [this message]
2003-06-21 6:36 ` Bernd Eckenfels
2003-06-21 7:42 ` Wichert Akkerman
2003-06-23 9:05 ` Lars Marowsky-Bree
2003-06-23 19:21 ` Paul Clements
2003-06-21 6:44 ` Andrew Morton
2003-06-21 15:59 ` Lou Langholtz
2003-06-21 7:04 ` Pavel Machek
2003-06-21 7:32 ` viro
2003-06-21 7:45 ` Sam Ravnborg
2003-06-21 16:39 ` Lou Langholtz
2003-06-21 19:31 ` viro
2003-06-21 20:23 ` Lou Langholtz
2003-06-22 10:30 ` Jens Axboe
2003-06-22 14:15 ` Lou Langholtz
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=20030621062306.GA140@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ldl@aros.net \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@chygwyn.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