DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
	"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fix broken rte strerror
Date: Fri, 2 Nov 2018 17:20:21 +0000	[thread overview]
Message-ID: <b0b1090b-0a34-5fb0-84e4-fb86738842c9@intel.com> (raw)
In-Reply-To: <1877297.2k9xseoUcZ@xps>

On 11/2/2018 9:41 AM, Thomas Monjalon wrote:
> 02/11/2018 09:11, Jerin Jacob:
>> errno_autotest testcase were failed since
>> commit 5d7b673d5fd6 ("mk: build with _GNU_SOURCE defined by default")
>> RTE>>errno_autotest
>> rte_strerror: 'Unknown error 11',
>> strerror: 'Resource temporarily unavailable'
>> Test Failed
>>
>> There are two different version of strerror_t() based on
>> _GNU_SOURCE definition.
>>
>> /* XSI-compliant */
>> int strerror_r(int errnum, char *buf, size_t buflen);
>>
>> /* GNU-specific */
>> char *strerror_r(int errnum, char *buf, size_t buflen);
>>
>> Since the GNU-specific version returns char* the exiting "if"
>> condition around the strerror_r fails.
>>
>> Switching back to XSI-compliant version to allow
>>
>> a) Portable strerror_r() usage as musl c library uses
>> non GNU speficic version
>> https://git.musl-libc.org/cgit/musl/tree/src/string/strerror_r.c
>>
>> b) Based on strerror_r(3) man page, it is possible that GNU-specific
>> version need not use char *buf to fill error message instead it
>> can use the immutable static string from the library and return it.
>>
>> note from strerror_r(3) man page:
>>
>> The GNU-specific strerror_r() returns a pointer to a string containing
>> the error message.  This may be either a pointer to a string that the
>> function stores in buf, or a pointer to some (immutable)
>> static string (in which case buf is unused).
>>
>> Fixes: 5d7b673d5fd6 ("mk: build with _GNU_SOURCE defined by default")
>>
>> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> 
> You may be interested by this patch from Ferruh:
> 	https://patches.dpdk.org/patch/47622/

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2018-11-02 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02  8:11 Jerin Jacob
2018-11-02  9:41 ` Thomas Monjalon
2018-11-02 17:20   ` Ferruh Yigit [this message]
2018-11-04 21:22     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0b1090b-0a34-5fb0-84e4-fb86738842c9@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).