From: Nicolas Schier <nicolas.schier@linux.dev>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>
Cc: masahiroy@kernel.org, linux-kbuild@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] kconfig/lxdialog: replace strcpy() with strncpy() in inputbox.c
Date: Sun, 27 Jul 2025 21:19:12 +0200 [thread overview]
Message-ID: <aIZ7sDZdHAOg2cf_@fjasle.eu> (raw)
In-Reply-To: <20250727164433.203775-1-suchitkarunakaran@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Sun, Jul 27, 2025 at 10:14:33PM +0530 Suchit Karunakaran wrote:
> strcpy() performs no bounds checking and can lead to buffer overflows if
> the input string exceeds the destination buffer size. This patch replaces
> it with strncpy(), and null terminates the input string.
>
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
> ---
> scripts/kconfig/lxdialog/inputbox.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Reviewed-by: Nicolas Schier <nicolas.schier@linux.dev>
thanks for your contribution!
If you want to continue contributing, you might want to check-out tools
like b4 which simplifies sending and tracking patch-sets.
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-07-27 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 16:44 [PATCH v3] kconfig/lxdialog: replace strcpy() with strncpy() in inputbox.c Suchit Karunakaran
2025-07-27 19:19 ` Nicolas Schier [this message]
2025-07-28 3:59 ` Suchit K
2025-07-28 4:29 ` Greg KH
2025-07-28 4:48 ` Suchit K
2025-07-28 5:20 ` Greg KH
[not found] ` <CAO9wTFi+atf1vwMrDJBa-X4W5UcQ8K80spgiGhMyhZj4aRJ3Zw@mail.gmail.com>
2025-07-28 5:39 ` Suchit K
2025-07-29 13:40 ` Masahiro Yamada
2025-07-29 13:41 ` Masahiro Yamada
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=aIZ7sDZdHAOg2cf_@fjasle.eu \
--to=nicolas.schier@linux.dev \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=suchitkarunakaran@gmail.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