From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: s3c: Use strscpy to replace strlcpy
Date: Mon, 6 Sep 2021 15:57:44 +0200 [thread overview]
Message-ID: <6ca0d3e1-b895-e6c8-e075-786f24c19696@canonical.com> (raw)
In-Reply-To: <20210906134656.101088-1-wangborong@cdjrlc.com>
On 06/09/2021 15:46, Jason Wang wrote:
> The strlcpy should not be used because it doesn't limit the source
> length. As linus says, it's a completely useless function if you
> can't implicitly trust the source string - but that is almost always
> why people think they should use it! All in all the BSD function
> will lead some potential bugs.
>
> But the strscpy doesn't require reading memory from the src string
> beyond the specified "count" bytes, and since the return value is
> easier to error-check than strlcpy()'s. In addition, the implementation
> is robust to the string changing out from underneath it, unlike the
> current strlcpy() implementation.
>
> Thus, We prefer using strscpy instead of strlcpy.
Don't copy-paste kernel documentation into commits. It's enough to say
that strlcpy is preferred, according to the kernel coding style (see
strlcpy()).
If you want to add more sentences, make them relevant, e.g. describe
possible effect of bugs depending on the source.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-09-06 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 13:46 [PATCH] ARM: s3c: Use strscpy to replace strlcpy Jason Wang
2021-09-06 13:57 ` Krzysztof Kozlowski [this message]
2021-09-20 8:15 ` Krzysztof Kozlowski
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=6ca0d3e1-b895-e6c8-e075-786f24c19696@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=wangborong@cdjrlc.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