From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: fix API to get error string Date: Wed, 31 Oct 2018 18:16:20 +0100 Message-ID: <5469782.njCRi2Lb0J@xps> References: <20181031171928.61110-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Bruce Richardson , stable@dpdk.org To: Ferruh Yigit Return-path: In-Reply-To: <20181031171928.61110-1-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 31/10/2018 18:19, Ferruh Yigit: > rte_strerror uses strerror_r(), and strerror_r() has two version of it. > - XSI-compliant version, (_POSIX_C_SOURCE >= 200112L) && ! _GNU_SOURCE > - GNU-specific version > > Those two has different return types, so the exiting return type check > is not correct for GNU-specific version. > > And this is causing failure in errno_autotest unit test. > > Adding different implementation for FreeBSD and Linux. > > Fixes: 016c32bd3e3d ("eal: cleanup strerror function") > Cc: stable@dpdk.org > > Signed-off-by: Ferruh Yigit > --- > --- a/lib/librte_eal/common/eal_common_errno.c > +++ b/lib/librte_eal/common/eal_common_errno.c > default: > +#ifdef RTE_EXEC_ENV_BSDAPP > if (strerror_r(errnum, ret, RETVAL_SZ) != 0) > snprintf(ret, RETVAL_SZ, "Unknown error%s %d", > sep, errnum); > +#else > + /* > + * _GNU_SOURCE version, error string is not always > + * strored in "ret" buffer, need to use return value > + */ > + ret = strerror_r(errnum, ret, RETVAL_SZ); > +#endif Why not use the return value in both cases? Why not writing an error message in Linux case?