From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 05/14] NFSD: move from strlcpy with unused retval to strscpy
Date: Fri, 19 Aug 2022 07:41:17 +0200 [thread overview]
Message-ID: <Yv8iffnImlzwscPG@shikoro> (raw)
In-Reply-To: <45B86549-7FA6-4E09-9739-4756FBD830BC@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
> > 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>
>
> Makes sense.
>
> I think I would like to carry 05 and 07 in the NFSD tree so they
> can get some exposure to our test workloads before they are merged.
> Is that OK with you?
Of course!
Thank you.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-19 5:41 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 [this message]
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 ` [PATCH 01/14] vboxsf: " Hans de Goede
2022-08-20 8:18 ` 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=Yv8iffnImlzwscPG@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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