From: Rob Landley <rob@landley.net>
To: Paul Clements <paul.clements@steeleye.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
paul.clements@steeleye.com, nbd-general@lists.sourceforge.net
Subject: Re: [PATCH] nbd: correct disconnect behavior
Date: Thu, 20 Jun 2013 22:56:30 -0500 [thread overview]
Message-ID: <1371786990.2776.137@driftwood> (raw)
In-Reply-To: <20130619210918.DF616222D8@clements> (from paul.clements@steeleye.com on Wed Jun 19 16:09:18 2013)
On 06/19/2013 04:09:18 PM, Paul Clements wrote:
> Currently, when a disconnect is requested by the user (via
> NBD_DISCONNECT
> ioctl) the return from NBD_DO_IT is undefined (it is usually one of
> several error codes). This means that nbd-client does not know if a
> manual disconnect was performed or whether a network error occurred.
> Because of this, nbd-client's persist mode (which tries to reconnect
> after
> error, but not after manual disconnect) does not always work
> correctly.
>
> This change fixes this by causing NBD_DO_IT to always return 0 if a
> user
> requests a disconnect. This means that nbd-client can correctly either
> persist the connection (if an error occurred) or disconnect (if the
> user
> requested it).
>
> Signed-off-by: Paul Clements <paul.clements@steeleye.com>
Is _that_ what it was?
(Guy who wrote the busybox NBD client and never did quite understand
the disconnect/reconnect behavior.)
Acked-by: Rob Landley <rob@landley.net>
Rob
next prev parent reply other threads:[~2013-06-21 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:09 [PATCH] nbd: correct disconnect behavior Paul Clements
2013-06-21 3:56 ` Rob Landley [this message]
2013-06-26 23:21 ` Andrew Morton
[not found] ` <CAECXXi54NUvQLY1O0oWKqgDpdXWUCCcs_4jJkRJE29DctMYVUA@mail.gmail.com>
2013-06-27 22:28 ` Andrew Morton
2013-06-27 23:25 ` Paul Clements
2013-07-02 7:19 ` Rob Landley
2013-08-26 12:54 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 22:24 Paul Clements
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=1371786990.2776.137@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=paul.clements@steeleye.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