From: David Laight <david.laight.linux@gmail.com>
To: Justin Stitt <justinstitt@google.com>
Cc: Mariia Nikitash <mariianikitash@google.com>,
trondmy@kernel.org, anna@kernel.org, keescook@google.com,
linux-hardening@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, nikitash.mariiaw@gmail.com
Subject: Re: [PATCH] NFS: nfsroot: replace strlcat() with snprintf()
Date: Wed, 19 Aug 2026 11:22:54 +0100 [thread overview]
Message-ID: <20260819112254.3e7d2b9c@pumpkin> (raw)
In-Reply-To: <CAFhGd8rGren7EwjASppcx2WW8d-ky-T7k6mTxK-MpHfZmFTtbg@mail.gmail.com>
On Tue, 18 Aug 2026 14:05:41 -0700
Justin Stitt <justinstitt@google.com> wrote:
> Hi,
>
> On Tue, Aug 18, 2026 at 1:55 AM David Laight
> <david.laight.linux@gmail.com> wrote:
> >
> > On Fri, 14 Aug 2026 00:28:45 -0700
> > Mariia Nikitash <mariianikitash@google.com> wrote:
> >
> > > In preparation for removing the deprecated strlcat() API[1], replace its
> > > uses in root_nfs_cat() with snprintf().
> > >
> > > Build the separator and source string in a single call using the
> > > remaining space in the destination buffer. snprintf() returns the length
> > > it would have written excluding the terminating NUL, so comparing the
> > > return value against the remaining buffer space preserves the existing
> > > truncation check.
> > >
> > > Link: https://github.com/KSPP/linux/issues/370 [1]
> > > Signed-off-by: Mariia Nikitash <mariianikitash@google.com>
> > > ---
> > > fs/nfs/nfsroot.c | 8 ++++----
> > > 1 file changed, 4 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/fs/nfs/nfsroot.c b/fs/nfs/nfsroot.c
> > > index 432612d22437..e951fe731679 100644
> > > --- a/fs/nfs/nfsroot.c
> > > +++ b/fs/nfs/nfsroot.c
> > > @@ -173,12 +173,12 @@ static int __init root_nfs_cat(char *dest, const char *src,
> > > const size_t destlen)
> > > {
> > > size_t len = strlen(dest);
> > > + size_t remaining = destlen - len;
> > > + const char *sep = "";
> > >
> > > if (len && dest[len - 1] != ',')
> > > - if (strlcat(dest, ",", destlen) >= destlen)
> > > - return -1;
> > > -
> > > - if (strlcat(dest, src, destlen) >= destlen)
> > > + sep = ",";
> > > + if (snprintf(dest + len, remaining, "%s%s", sep, src) >= remaining)
> > > return -1;
> >
> > I think I'd have gone for:
> > size_t len = strlen(dest);
> > if (len && dest[len - 1] != ',' && ++len < destlen)
> > dest[len - 1] = ',';
> > if (strscpy(dest + len, src, destlen - len) < 0)
> > return -1;
>
> Can we run into underflow issues if `len == destlen` during the
> increment. imagine @len is 10 and @destlen is also 10. We end up
> incrementing len and our strscpy receives `10 - 11` wrapping to
> SIZE_MAX.
len can only be less than destlen, so strscpy() can only see a zero
length - which is fine,
This whole code could be rewritten to avoid the strlen().
The function is only used twice to append data to a single static string.
Tweaking the initialisation would allow sizeof() be used to set
the initial length.
The initialisation also means that the ',' is always needed.
The second call appends data from an snprintf() into a temporary buffer.
It wouldn't be hard to directly add the data to the actual buffer.
David
>
> Maybe this isn't reachable as @destlen may always be larger than what
> `strlen()` can give us but that increment looks suspicious.
>
> >
> > Although it would be better as an 'add_option()' function.
> > I suspect the it used to be just strcat().
> > (similarly for root_nfs_copy() which is a pointless wrapper on strscpy()).
> >
> > Much more worth while would be fixing the sprintf() for NFS_ROOT.
> >
> > David
> >
> > > return 0;
> > > }
> >
>
> Justin
prev parent reply other threads:[~2026-08-19 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 7:28 [PATCH] NFS: nfsroot: replace strlcat() with snprintf() Mariia Nikitash
2026-08-17 20:33 ` Justin Stitt
2026-08-17 20:51 ` Bill Wendling
2026-08-18 8:55 ` David Laight
2026-08-18 17:42 ` Kees Cook
2026-08-18 18:44 ` Mariia Nikitash
2026-08-18 21:05 ` Justin Stitt
2026-08-19 10:22 ` David Laight [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=20260819112254.3e7d2b9c@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=anna@kernel.org \
--cc=justinstitt@google.com \
--cc=keescook@google.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mariianikitash@google.com \
--cc=nikitash.mariiaw@gmail.com \
--cc=trondmy@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