From: Thorsten Blum <thorsten.blum@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <danielt@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Nir Lichtman <nir@lichtman.org>,
Yuran Pereira <yuran.pereira@hotmail.com>,
linux-hardening@vger.kernel.org,
Daniel Thompson <daniel@riscstar.com>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdb: Replace deprecated strcpy() with strscpy()
Date: Thu, 14 Aug 2025 17:17:52 +0200 [thread overview]
Message-ID: <55A7B251-8E1B-4935-B33F-B12DF1A2B382@linux.dev> (raw)
In-Reply-To: <2025081456-reflected-revolver-9f5b@gregkh>
Hi Greg,
On 14. Aug 2025, at 16:35, Greg Kroah-Hartman wrote:
> On Thu, Aug 14, 2025 at 02:35:56PM +0200, Greg Kroah-Hartman wrote:
>> On Thu, Aug 14, 2025 at 02:03:37PM +0200, Thorsten Blum wrote:
>>> [...]
>>> - strcpy(kdb_grep_string, cp);
>>> + strscpy(kdb_grep_string, cp);
>>
>> If this was just a search/replace, it would have been done already, so
>> why is this ok?
>
> I missed that strscpy() can now handle 2 arguments like this, so yes,
> this should be ok.
>
> BUT, you just checked the length above this line, which now isn't
> needed, right? So this function can get simpler?
Yes, this could just be
memcpy(kdb_grep_string, cp, len + 1);
because we already know the length which strscpy() would just recompute
before calling memcpy() internally. I'll submit a v2.
>>> - strscpy(cmd_cur, cmd_hist[cmdptr], CMD_BUFLEN);
>>> + strscpy(cmd_cur, cmd_hist[cmdptr]);
>>
>> Same here. And other places...
>
> Sorry, this should also be ok, BUT it's really just doing the same exact
> thing, right?
Yes, it's the same because sizeof(cmd_cur) equals CMD_BUFLEN.
Thanks,
Thorsten
next prev parent reply other threads:[~2025-08-14 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 12:03 Thorsten Blum
2025-08-14 12:35 ` Greg Kroah-Hartman
2025-08-14 14:35 ` Greg Kroah-Hartman
2025-08-14 15:17 ` Thorsten Blum [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 21:37 Thorsten Blum
2025-07-18 22:48 ` Doug Anderson
2025-08-18 11:02 ` Thorsten Blum
2025-08-18 16:17 ` Doug Anderson
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=55A7B251-8E1B-4935-B33F-B12DF1A2B382@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=daniel@riscstar.com \
--cc=danielt@kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@lichtman.org \
--cc=yuran.pereira@hotmail.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
all inboxes | Powered by JetHome®