From c33f3d5cba21c8cf267daab5450bc95ea7e68967 Mon Sep 17 00:00:00 2001
From: Derrell Lipman <derrell@dworkin.(none)>
Date: Fri, 27 Mar 2009 18:02:46 -0400
Subject: [Bug 6228] SMBC_open_ctx failure due to path resolve failure doesn't
 set errno

Fixed.

It turns out there were a number of places where cli_resolve_path() was called
and the error path upon that function failing did not set errno. There were a
couple of places the failure handling code did set errno to ENOENT, so I made
them all consistent, although I think better errno choices for this condition
exist, e.g.  EHOSTUNREACH.

Derrell
---
 source3/libsmb/libsmb_stat.c | 1 +
 1 file changed, 1 insertion(+)

(limited to 'source3/libsmb/libsmb_stat.c')

diff --git a/source3/libsmb/libsmb_stat.c b/source3/libsmb/libsmb_stat.c
index dc904d2753..c2806daddb 100644
--- a/source3/libsmb/libsmb_stat.c
+++ b/source3/libsmb/libsmb_stat.c
@@ -261,6 +261,7 @@ SMBC_fstat_ctx(SMBCCTX *context,
 			file->srv->cli, path,
 			&targetcli, &targetpath)) {
 		d_printf("Could not resolve %s\n", path);
+                errno = ENOENT;
 		TALLOC_FREE(frame);
 		return -1;
 	}
-- 
cgit