From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unicode: replace strncpy() by strscpy()
Date: Tue, 28 May 2019 13:47:49 -0400 [thread overview]
Message-ID: <8536kympx6.fsf@collabora.com> (raw)
In-Reply-To: <20190527174733.GA29547@embeddedor> (Gustavo A. R. Silva's message of "Mon, 27 May 2019 12:47:33 -0500")
"Gustavo A. R. Silva" <gustavo@embeddedor.com> writes:
> The strncpy() function is being deprecated. Replace it by the safer
> strscpy() and fix the following Coverity warning:
>
> "Calling strncpy with a maximum size argument of 12 bytes on destination
> array version_string of size 12 bytes might leave the destination string
> unterminated."
>
> Notice that, unlike strncpy(), strscpy() always null-terminates the
> destination string.
>
Thanks, I'll get this queued up.
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2019-05-28 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 17:47 [PATCH] unicode: replace strncpy() by strscpy() Gustavo A. R. Silva
2019-05-28 17:47 ` Gabriel Krisman Bertazi [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=8536kympx6.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=gustavo@embeddedor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).