From: Simon Horman <horms@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: torvalds@linux-foundation.org, ebiederm@xmission.com,
alexei.starovoitov@gmail.com, rostedt@goodmis.org,
catalin.marinas@arm.com, akpm@linux-foundation.org,
penguin-kernel@i-love.sakura.ne.jp, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, audit@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 06/11] mm/util: Deduplicate code in {kstrdup,kstrndup,kmemdup_nul}
Date: Fri, 21 Jun 2024 14:51:42 +0100 [thread overview]
Message-ID: <20240621135142.GF1098275@kernel.org> (raw)
In-Reply-To: <20240621022959.9124-7-laoar.shao@gmail.com>
On Fri, Jun 21, 2024 at 10:29:54AM +0800, Yafang Shao wrote:
> These three functions follow the same pattern. To deduplicate the code,
> let's introduce a common help __kstrndup().
>
> Suggested-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Hi Yafang Shao,
Some minor nits from my side.
> ---
> mm/internal.h | 24 ++++++++++++++++++++++++
> mm/util.c | 27 ++++-----------------------
> 2 files changed, 28 insertions(+), 23 deletions(-)
>
> diff --git a/mm/internal.h b/mm/internal.h
> index b2c75b12014e..fd87f685739b 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -1521,4 +1521,28 @@ static inline void shrinker_debugfs_remove(struct dentry *debugfs_entry,
> void workingset_update_node(struct xa_node *node);
> extern struct list_lru shadow_nodes;
>
> +/**
> + * __kstrndup - Create a NUL-terminated string from @s, which might be unterminated.
> + * @s: The data to stringify
> + * @len: The size of the data, including the null terminator
> + * @gfp: the GFP mask used in the kmalloc() call when allocating memory
> + *
> + * Return: newly allocated copy of @s with NUL-termination or %NULL in
> + * case of error
> + */
> +static __always_inline char *__kstrndup(const char *s, size_t len, gfp_t gfp)
> +{
> + char *buf;
> +
> + buf = kmalloc_track_caller(len, gfp);
> + if (!buf)
> + return NULL;
> +
> + memcpy(buf, s, len);
> + /* Ensure the buf is always NUL-terminated, regardless of @s. */
> + buf[len - 1] = '\0';
> + return buf;
> +}
> +
> +
nit: One blank line is enough.
> #endif /* __MM_INTERNAL_H */
> diff --git a/mm/util.c b/mm/util.c
> index 41c7875572ed..d9135c5fdf7f 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -58,17 +58,8 @@ char *kstrdup(const char *s, gfp_t gfp)
> if (!s)
> return NULL;
>
> - len = strlen(s) + 1;
> - buf = kmalloc_track_caller(len, gfp);
> - if (buf) {
> - memcpy(buf, s, len);
> - /* During memcpy(), the string might be updated to a new value,
> - * which could be longer than the string when strlen() is
> - * called. Therefore, we need to add a null termimator.
> - */
> - buf[len - 1] = '\0';
> - }
> - return buf;
nit: The local variable buf is now unused, and should be removed from kstrdup().
Likewise for kstrndup() and kmemdup_nul()
Flagged by W=1 builds with gcc-13 and clang-18, and Smatch.
> + len = strlen(s);
> + return __kstrndup(s, len + 1, gfp);
> }
> EXPORT_SYMBOL(kstrdup);
>
> @@ -111,12 +102,7 @@ char *kstrndup(const char *s, size_t max, gfp_t gfp)
> return NULL;
>
> len = strnlen(s, max);
> - buf = kmalloc_track_caller(len+1, gfp);
> - if (buf) {
> - memcpy(buf, s, len);
> - buf[len] = '\0';
> - }
> - return buf;
> + return __kstrndup(s, len + 1, gfp);
> }
> EXPORT_SYMBOL(kstrndup);
>
> @@ -195,12 +181,7 @@ char *kmemdup_nul(const char *s, size_t len, gfp_t gfp)
> if (!s)
> return NULL;
>
> - buf = kmalloc_track_caller(len + 1, gfp);
> - if (buf) {
> - memcpy(buf, s, len);
> - buf[len] = '\0';
> - }
> - return buf;
> + return __kstrndup(s, len + 1, gfp);
> }
> EXPORT_SYMBOL(kmemdup_nul);
>
> --
> 2.39.1
>
>
next prev parent reply other threads:[~2024-06-21 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 2:29 [PATCH v3 00/11] Improve the copy of task comm Yafang Shao
2024-06-21 2:29 ` [PATCH v3 01/11] fs/exec: Drop task_lock() inside __get_task_comm() Yafang Shao
2024-06-21 2:29 ` [PATCH v3 02/11] auditsc: Replace memcpy() with __get_task_comm() Yafang Shao
2024-06-21 2:29 ` [PATCH v3 03/11] security: " Yafang Shao
2024-06-21 2:29 ` [PATCH v3 04/11] bpftool: Ensure task comm is always NUL-terminated Yafang Shao
2024-06-21 2:29 ` [PATCH v3 05/11] mm/util: Fix possible race condition in kstrdup() Yafang Shao
2024-06-21 2:29 ` [PATCH v3 06/11] mm/util: Deduplicate code in {kstrdup,kstrndup,kmemdup_nul} Yafang Shao
2024-06-21 13:51 ` Simon Horman [this message]
2024-06-23 2:26 ` Yafang Shao
2024-06-21 13:57 ` Matthew Wilcox
2024-06-23 2:29 ` Yafang Shao
2024-06-23 3:11 ` Matthew Wilcox
2024-06-23 6:00 ` Yafang Shao
2024-06-21 2:29 ` [PATCH v3 07/11] mm/kmemleak: Replace strncpy() with __get_task_comm() Yafang Shao
2024-06-21 2:29 ` [PATCH v3 08/11] tsacct: " Yafang Shao
2024-06-21 2:29 ` [PATCH v3 09/11] tracing: " Yafang Shao
2024-06-21 4:37 ` Masami Hiramatsu
2024-06-21 2:29 ` [PATCH v3 10/11] net: Replace strcpy() " Yafang Shao
2024-06-21 2:29 ` [PATCH v3 11/11] drm: " Yafang Shao
2024-06-21 16:39 ` Daniel Vetter
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=20240621135142.GF1098275@kernel.org \
--to=horms@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=audit@vger.kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=laoar.shao@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rostedt@goodmis.org \
--cc=selinux@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).