From: <guo.ziliang@zte.com.cn>
To: <gregkh@linuxfoundation.org>
Cc: <tj@kernel.org>, <linux-kernel@vger.kernel.org>,
<guo.ziliang@zte.com.cn>
Subject: [PATCH linux-next] kernfs: use strscpy() is more robust and safer
Date: Tue, 15 Nov 2022 08:47:45 +0800 (CST) [thread overview]
Message-ID: <202211150847452601249@zte.com.cn> (raw)
From: guo ziliang <guo.ziliang@zte.com.cn>
The implementation of strscpy() is more robust and safer. That's now the
recommended way to copy NUL terminated strings.
Signed-off-by: guo ziliang <guo.ziliang@zte.com.cn>
---
fs/kernfs/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c
index 77d7a3a..fbb8df4 100644
--- a/fs/kernfs/dir.c
+++ b/fs/kernfs/dir.c
@@ -844,7 +844,7 @@ static struct kernfs_node *kernfs_walk_ns(struct kernfs_node *parent,
spin_lock_irq(&kernfs_pr_cont_lock);
- len = strlcpy(kernfs_pr_cont_buf, path, sizeof(kernfs_pr_cont_buf));
+ len = strscpy(kernfs_pr_cont_buf, path, sizeof(kernfs_pr_cont_buf));
if (len >= sizeof(kernfs_pr_cont_buf)) {
spin_unlock_irq(&kernfs_pr_cont_lock);
--
1.8.3.1
next reply other threads:[~2022-11-15 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 0:47 guo.ziliang [this message]
2022-11-15 6:43 ` [PATCH linux-next] kernfs: use strscpy() is more robust and safer Greg KH
2022-11-15 10:32 ` Greg KH
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=202211150847452601249@zte.com.cn \
--to=guo.ziliang@zte.com.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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