From: Chao Yu <chao@kernel.org>
To: Daniel Yang <danielyangkang@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
"open list:F2FS FILE SYSTEM"
<linux-f2fs-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Cc: Chao Yu <chao@kernel.org>
Subject: Re: [PATCH] parse_options(): replace deprecated strcpy with strscpy
Date: Fri, 8 Nov 2024 17:46:54 +0800 [thread overview]
Message-ID: <a1471ca1-e119-4106-8965-cd954c373a62@kernel.org> (raw)
In-Reply-To: <20241106025858.495458-1-danielyangkang@gmail.com>
On 2024/11/6 10:58, Daniel Yang wrote:
> strcpy is deprecated. Kernel docs recommend replacing strcpy with
> strscpy. The function strcpy() return value isn't used so there
> shouldn't be an issue replacing with the safer alternative strscpy.
It's better to add "f2fs: " prefix for commit title.
>
> Signed-off-by: Daniel Yang <danielyangkang@gmail.com>
> ---
> fs/f2fs/super.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index 87ab5696b..ee8861b95 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1158,7 +1158,7 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> break;
> }
>
> - strcpy(ext[ext_cnt], name);
> + strscpy(ext[ext_cnt], name);
Needs to handle return value of strscpy()?
> F2FS_OPTION(sbi).compress_ext_cnt++;
> kfree(name);
> break;
> @@ -1187,7 +1187,7 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> break;
> }
>
> - strcpy(noext[noext_cnt], name);
> + strscpy(noext[noext_cnt], name);
Ditto,
Thanks,
> F2FS_OPTION(sbi).nocompress_ext_cnt++;
> kfree(name);
> break;
next prev parent reply other threads:[~2024-11-08 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 2:58 [PATCH] parse_options(): replace deprecated strcpy with strscpy Daniel Yang
2024-11-08 9:46 ` Chao Yu [this message]
2024-11-09 1:40 ` Daniel Yang
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=a1471ca1-e119-4106-8965-cd954c373a62@kernel.org \
--to=chao@kernel.org \
--cc=danielyangkang@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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