From: Thorsten Blum <thorsten.blum@linux.dev>
To: Daniel Thompson <daniel@riscstar.com>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <danielt@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Nir Lichtman <nir@lichtman.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yuran Pereira <yuran.pereira@hotmail.com>,
linux-hardening@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] kdb: Replace deprecated strcpy() with strscpy() and memcpy()
Date: Fri, 15 Aug 2025 16:40:56 +0200 [thread overview]
Message-ID: <73C106D1-C7F8-415C-9BC2-89607C839265@linux.dev> (raw)
In-Reply-To: <aJ9EPQNk2bcOMP1h@aspen.lan>
On 15. Aug 2025, at 16:29, Daniel Thompson wrote:
>
> I like the extra diligence of checking the trailing quote but perhaps
> combine the two if statements (so we only chomp the quotes if there
> are two).
Ok.
Should I replace kdb_strdup() with kdb_strdup_dequote() because it also
handles unquoted strings or do we want to keep both versions? It's only
used in a few places where kdb_strdup_dequote() would also work.
Thanks,
Thorsten
prev parent reply other threads:[~2025-08-15 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 22:01 [PATCH v3] kdb: Replace deprecated strcpy() with strscpy() and memcpy() Thorsten Blum
2025-08-15 2:05 ` Doug Anderson
2025-08-15 10:48 ` Thorsten Blum
2025-08-15 14:32 ` Doug Anderson
2025-08-15 8:57 ` Daniel Thompson
2025-08-15 11:28 ` Thorsten Blum
2025-08-15 11:40 ` Daniel Thompson
2025-08-15 13:16 ` Thorsten Blum
2025-08-15 14:29 ` Daniel Thompson
2025-08-15 14:40 ` Thorsten Blum [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=73C106D1-C7F8-415C-9BC2-89607C839265@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.