From: Kees Cook <keescook@chromium.org>
To: Azeem Shaikh <azeemshaikh38@gmail.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
linux-hardening@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFS: Prefer strscpy over strlcpy calls
Date: Tue, 16 May 2023 14:04:20 -0700 [thread overview]
Message-ID: <202305161403.15ED4EC@keescook> (raw)
In-Reply-To: <20230512155749.1356958-1-azeemshaikh38@gmail.com>
On Fri, May 12, 2023 at 03:57:49PM +0000, Azeem Shaikh wrote:
> strlcpy() reads the entire source buffer first.
> This read may exceed the destination size limit.
> This is both inefficient and can lead to linear read
> overflows if a source string is not NUL-terminated [1].
> Check for strscpy()'s return value of -E2BIG on truncate for safe
> replacement with strlcpy().
>
> This is part of a tree-wide cleanup to remove the strlcpy() function
> entirely from the kernel [2].
>
> [1] https://www.kernel.org/doc/html/latest/process/deprecated.html#strlcpy
> [2] https://github.com/KSPP/linux/issues/89
>
> Signed-off-by: Azeem Shaikh <azeemshaikh38@gmail.com>
> ---
> Note to reviewers: the one case where this patch would modify existing behavior
> is when strlen(src)==destlen==0. Current behavior returns 0, with this patch it
> would return -1.
>
> Not sure what the implication of this updated behavior would be,
> so bringing it to your attention.
I'm not sure either, but I would prefer non-terminated strings produce
an error, which this change does. :)
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
>
> fs/nfs/nfsroot.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfs/nfsroot.c b/fs/nfs/nfsroot.c
> index 620329b7e6ae..7600100ba26f 100644
> --- a/fs/nfs/nfsroot.c
> +++ b/fs/nfs/nfsroot.c
> @@ -164,7 +164,7 @@ __setup("nfsroot=", nfs_root_setup);
> static int __init root_nfs_copy(char *dest, const char *src,
> const size_t destlen)
> {
> - if (strlcpy(dest, src, destlen) > destlen)
> + if (strscpy(dest, src, destlen) == -E2BIG)
> return -1;
> return 0;
> }
> --
> 2.40.1.606.ga4b1b128d6-goog
>
>
--
Kees Cook
next prev parent reply other threads:[~2023-05-16 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:57 [PATCH] NFS: Prefer strscpy over strlcpy calls Azeem Shaikh
2023-05-16 21:04 ` Kees Cook [this message]
2023-05-22 16:19 ` Azeem Shaikh
2023-05-22 19:39 ` Kees Cook
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=202305161403.15ED4EC@keescook \
--to=keescook@chromium.org \
--cc=anna@kernel.org \
--cc=azeemshaikh38@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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