From: Steven Rostedt <rostedt@goodmis.org>
To: Devaansh Kumar <devaanshk840@gmail.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v2] tracing: Replace deprecated strncpy() with strscpy() for stack_trace_filter_buf
Date: Fri, 4 Apr 2025 09:46:32 -0400 [thread overview]
Message-ID: <20250404094632.26f5b7c0@gandalf.local.home> (raw)
In-Reply-To: <20250404133105.2660762-1-devaanshk840@gmail.com>
On Fri, 4 Apr 2025 19:01:03 +0530
Devaansh Kumar <devaanshk840@gmail.com> wrote:
> strncpy() is deprecated for NUL-terminated destination buffers and must
> be replaced by strscpy().
>
> See issue: https://github.com/KSPP/linux/issues/90
>
> Signed-off-by: Devaansh Kumar <devaanshk840@gmail.com>
> ---
> kernel/trace/trace_stack.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c
> index 5a48dba912ea..982b1c88fce2 100644
> --- a/kernel/trace/trace_stack.c
> +++ b/kernel/trace/trace_stack.c
> @@ -3,6 +3,7 @@
> * Copyright (C) 2008 Steven Rostedt <srostedt@redhat.com>
> *
> */
> +#include <linux/string.h>
> #include <linux/sched/task_stack.h>
> #include <linux/stacktrace.h>
> #include <linux/security.h>
Is string.h really needed here? And if so, please keep the upside-down
x-mas tree format:
#include <linux/sched/task_stack.h>
#include <linux/stacktrace.h>
#include <linux/security.h>
#include <linux/kallsyms.h>
#include <linux/seq_file.h>
#include <linux/spinlock.h>
#include <linux/uaccess.h>
#include <linux/ftrace.h>
#include <linux/module.h>
#include <linux/sysctl.h>
#include <linux/init.h>
The includes *are* ordered.
-- Steve
next prev parent reply other threads:[~2025-04-04 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 13:31 [PATCH v2] tracing: Replace deprecated strncpy() with strscpy() for stack_trace_filter_buf Devaansh Kumar
2025-04-04 13:46 ` Steven Rostedt [this message]
2025-04-04 13:57 ` Devaansh Kumar
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=20250404094632.26f5b7c0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=devaanshk840@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=skhan@linuxfoundation.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