From cf63a76ca03240eb617ca5bd2aa9b3f7abe7b6a4 Mon Sep 17 00:00:00 2001 From: Emmanuel Dreyfus Date: Sat, 20 Oct 2012 19:30:06 +0200 Subject: NetBSD negative timeout missing support workaround Newer and simplier version: since the default of negative_timeout is 0, we can just avoid sending a fuse_entry in that case, and this is enough to work around the problem. BUG: 764655 Change-Id: Ibfc6230e3cb9871ccade7fb756e61ebc47cb6487 Signed-off-by: Emmanuel Dreyfus Reviewed-on: http://review.gluster.org/4115 Reviewed-by: Anand Avati Tested-by: Anand Avati --- xlators/mount/fuse/src/fuse-bridge.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'xlators/mount') diff --git a/xlators/mount/fuse/src/fuse-bridge.c b/xlators/mount/fuse/src/fuse-bridge.c index e46283793..664017d6b 100644 --- a/xlators/mount/fuse/src/fuse-bridge.c +++ b/xlators/mount/fuse/src/fuse-bridge.c @@ -364,7 +364,7 @@ fuse_entry_cbk (call_frame_t *frame, void *cookie, xlator_t *this, "%"PRIu64": %s() %s => -1 (%s)", frame->root->unique, gf_fop_list[frame->root->op], state->loc.path, strerror (op_errno)); - if (op_errno == ENOENT) { + if ((op_errno == ENOENT) && (priv->negative_timeout != 0)) { feo.entry_valid = calc_timeout_sec (priv->negative_timeout); feo.entry_valid_nsec = -- cgit