linux-kernel - Re: [PATCH] xtensa: use strscpy to copy strings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMo8BfLnPFWwOZTpycKfRuGvYV2wumtPxv9n2UjkM0s3LBB-9w@mail.gmail.com>
Date:   Fri, 24 Dec 2021 03:28:07 -0800
From:   Max Filippov <jcmvbkbc@...il.com>
To:     Jason Wang <wangborong@...rlc.com>
Cc:     Chris Zankel <chris@...kel.net>,
        Randy Dunlap <rdunlap@...radead.org>,
        "open list:TENSILICA XTENSA PORT (xtensa)" 
        <linux-xtensa@...ux-xtensa.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] xtensa: use strscpy to copy strings

On Mon, Dec 20, 2021 at 12:50 AM Jason Wang <wangborong@...rlc.com> wrote:
>
> The strlcpy should not be used because it doesn't limit the source
> length. So that it 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, replace strlcpy with strscpy.
>
> Signed-off-by: Jason Wang <wangborong@...rlc.com>
> ---
>  arch/xtensa/kernel/setup.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Applied to my xtensa tree. Thanks.

-- Max