Always check for ENODATA with ENOATTR

Linux defines ENODATA and ENOATTR with the same value, which means that code can miss on on the two without breaking. FreeBSD does not have ENODATA and GlusterFS defines it as ENOATTR just like Linux does. On NetBSD, ENODATA != ENOATTR, hence we need to check for both values to get portable behavior. BUG: 764655 Change-Id: I003a3af055fdad285d235f2a0c192c9cce56fab8 Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org> Reviewed-on: http://review.gluster.org/8447 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Niels de Vos <ndevos@redhat.com>
0 files changed, 0 insertions, 0 deletions
diff --git a/libglusterfs/src/compat-errno.c b/libglusterfs/src/compat-errno.c
index fd5cc49cefa..d8ab82a5d20 100644
--- a/libglusterfs/src/compat-errno.c
+++ b/libglusterfs/src/compat-errno.c
@@ -859,6 +859,12 @@ init_compat_errno_arrays ()
         gf_error_to_errno_array[GF_ERROR_CODE_BADMSG] = EBADMSG;
         gf_errno_to_error_array[EBADMSG] = GF_ERROR_CODE_BADMSG;
 
+#ifdef __NetBSD__
+        /*      ENODATA         89              / * No message available */
+        gf_error_to_errno_array[GF_ERROR_CODE_NODATA] = ENODATA;
+        gf_errno_to_error_array[ENODATA] = GF_ERROR_CODE_NODATA;
+#endif
+
         /*      EMULTIHOP       90              / * Multihop attempted */
         gf_error_to_errno_array[GF_ERROR_CODE_MULTIHOP] = EMULTIHOP;
         gf_errno_to_error_array[EMULTIHOP] = GF_ERROR_CODE_MULTIHOP;