From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53061) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d1EDl-0004j8-TJ for qemu-devel@nongnu.org; Thu, 20 Apr 2017 11:42:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d1EDl-0000Ml-6L for qemu-devel@nongnu.org; Thu, 20 Apr 2017 11:42:13 -0400 Date: Thu, 20 Apr 2017 11:42:00 -0400 From: Jeff Cody Message-ID: <20170420154200.GK15762@localhost.localdomain> References: <20170420040003.31074-1-famz@redhat.com> <20170420153016.GI3227@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170420153016.GI3227@redhat.com> Subject: Re: [Qemu-devel] [PATCH] sheepdog: Set error when connection fails List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Fam Zheng , qemu-devel@nongnu.org, Kevin Wolf , sheepdog@lists.wpkg.org, qemu-block@nongnu.org, Hitoshi Mitake , Max Reitz , Liu Yuan On Thu, Apr 20, 2017 at 04:30:16PM +0100, Daniel P. Berrange wrote: > On Thu, Apr 20, 2017 at 12:00:03PM +0800, Fam Zheng wrote: > > Signed-off-by: Fam Zheng > > --- > > block/sheepdog.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/block/sheepdog.c b/block/sheepdog.c > > index fb9203e..7e889ee 100644 > > --- a/block/sheepdog.c > > +++ b/block/sheepdog.c > > @@ -608,6 +608,7 @@ static int connect_to_sdog(BDRVSheepdogState *s, Error **errp) > > qemu_set_nonblock(fd); > > } else { > > fd = -EIO; > > + error_setg(errp, "Failed to connect to sheepdog server"); > > } > > This doesn't make much sense to me. The lines just above the > diff context have this: > > fd = socket_connect(s->addr, errp, NULL, NULL); > > socket_connect should have already reported an error on "errp" > in the scenario that 'fd == -1'. So AFAICT the new error_setg is > just throwing away the real detailed error message in favour of > a generic message. > > So I'm puzzelled why we need to change anything - error reporting > should already be working fine. > Indeed, you are right. (Dequeuing patch) It would also make more sense to check fd after the socket_connect() call and return error then, rather than keep checking fd throughout the rest of the function. -Jeff