From: Hans de Goede <hdegoede@redhat.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 01/14] vboxsf: move from strlcpy with unused retval to strscpy
Date: Fri, 19 Aug 2022 11:01:44 +0200 [thread overview]
Message-ID: <0d44fb03-0481-2f0d-eeb5-63cbddeffc62@redhat.com> (raw)
In-Reply-To: <20220818210123.7637-1-wsa+renesas@sang-engineering.com>
Hi,
On 8/18/22 23:01, Wolfram Sang wrote:
> Follow the advice of the below link and prefer 'strscpy' in this
> subsystem. Conversion is 1:1 because the return value is not used.
> Generated by a coccinelle script.
>
> Link: https://lore.kernel.org/r/CAHk-=wgfRnXz0W3D37d01q3JFkr_i_uTL=V6A6G1oUZcprmknw@mail.gmail.com/
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Note you send this one twice. Since I'm not sure which one
will end up getting merged, I'm going to just reply to both...
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> fs/vboxsf/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/vboxsf/super.c b/fs/vboxsf/super.c
> index d2f6df69f611..1fb8f4df60cb 100644
> --- a/fs/vboxsf/super.c
> +++ b/fs/vboxsf/super.c
> @@ -176,7 +176,7 @@ static int vboxsf_fill_super(struct super_block *sb, struct fs_context *fc)
> }
> folder_name->size = size;
> folder_name->length = size - 1;
> - strlcpy(folder_name->string.utf8, fc->source, size);
> + strscpy(folder_name->string.utf8, fc->source, size);
> err = vboxsf_map_folder(folder_name, &sbi->root);
> kfree(folder_name);
> if (err) {
next prev parent reply other threads:[~2022-08-19 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:01 [PATCH 01/14] vboxsf: move from strlcpy with unused retval to strscpy Wolfram Sang
2022-08-18 21:01 ` [PATCH 02/14] reiserfs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 03/14] proc: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 04/14] ocfs2: " Wolfram Sang
2022-08-21 13:24 ` Joseph Qi
2022-08-18 21:01 ` [PATCH 05/14] NFSD: " Wolfram Sang
2022-08-18 21:08 ` Chuck Lever III
2022-08-19 5:41 ` Wolfram Sang
2022-08-18 21:01 ` [PATCH 06/14] NFS: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 07/14] lockd: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 08/14] hostfs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 09/14] gfs2: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 10/14] dlm: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 11/14] cifs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 12/14] befs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 13/14] affs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 14/14] fs: " Wolfram Sang
2022-08-19 9:01 ` Hans de Goede [this message]
2022-08-20 8:18 ` [PATCH 01/14] vboxsf: " Wolfram Sang
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=0d44fb03-0481-2f0d-eeb5-63cbddeffc62@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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