From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nfs-utils: fix a Gcc undefined behavior
Date: Tue, 21 Oct 2014 08:10:18 +0800 [thread overview]
Message-ID: <5445A46A.5050505@windriver.com> (raw)
In-Reply-To: <CAJTo0LZ3p9R2CUnj_XffSQDoDE-_Cg8pmLBQ_VDu5p9TSxYc-Q@mail.gmail.com>
On 10/20/2014 06:59 PM, Burton, Ross wrote:
> On 15 October 2014 10:21, <rongqing.li@windriver.com> wrote:
>> Calling strncpy with NULL second argument, even when the size is 0,
>> is undefined behavior, which leads to GCC to drop the check old
>> variable with NULL in following code.
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6743
>
> I've merged this into my MUT branch but we're very late for 1.7.0
> unless it's a critical fix. We can roll this into 1.7.1 though.
>
> Ross
>
It make the nfs-server unable to start up on my test environment
-Roy
--
Best Reagrds,
Roy | RongQing Li
prev parent reply other threads:[~2014-10-21 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 9:21 [PATCH] nfs-utils: fix a Gcc undefined behavior rongqing.li
2014-10-20 3:22 ` Rongqing Li
2014-10-20 3:39 ` Khem Raj
2014-10-20 10:59 ` Burton, Ross
2014-10-21 0:10 ` Rongqing Li [this message]
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=5445A46A.5050505@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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