linux-kernel - Re: [PATCH] nbd: correct disconnect behavior

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Jun 2013 22:56:30 -0500
From:	Rob Landley <rob@...dley.net>
To:	Paul Clements <paul.clements@...eleye.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	paul.clements@...eleye.com, nbd-general@...ts.sourceforge.net
Subject: Re: [PATCH] nbd: correct disconnect behavior

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@...eleye.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@...dley.net>

Rob--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/