From eb705e090a4748efd18279ad920b2db295f2075a Mon Sep 17 00:00:00 2001
From: Niels de Vos <ndevos@redhat.com>
Date: Mon, 16 May 2016 19:53:44 +0200
Subject: core: correct the if-statment in inode_set_need_lookup()

There does not seem to be an ill side-effect from the incorrect
if-statement. But we should really stick to the same checks we do
everywhere.

BUG: 1236009
Change-Id: If2b787287ac0d87712840b15b8c914e3dc5ffcde
Reported-by: kinsu <vpolakis@gmail.com>
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: http://review.gluster.org/14363
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
---
 libglusterfs/src/inode.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libglusterfs/src/inode.c b/libglusterfs/src/inode.c
index ab4b505e22f..6d79ac2d3f9 100644
--- a/libglusterfs/src/inode.c
+++ b/libglusterfs/src/inode.c
@@ -1887,7 +1887,7 @@ inode_set_need_lookup (inode_t *inode, xlator_t *this)
 {
         uint64_t  need_lookup = LOOKUP_NEEDED;
 
-        if (!inode | !this)
+        if (!inode || !this)
                 return;
 
         inode_ctx_set (inode, this, &need_lookup);
-- 
cgit