From: Steven Rostedt <rostedt@goodmis.org>
To: Hui Su <sh_def@163.com>
Cc: mingo@redhat.com, jack@suse.cz, akpm@linux-foundation.org,
neilb@suse.de, tj@kernel.org, trond.myklebust@hammerspace.com,
liuzhiqiang26@huawei.com, tytso@mit.edu, cai@lca.pw,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: fix potenial dangerous pointer
Date: Tue, 24 Nov 2020 12:05:23 -0500 [thread overview]
Message-ID: <20201124120523.34a59eed@gandalf.local.home> (raw)
In-Reply-To: <20201124165205.GA23937@rlk>
On Wed, 25 Nov 2020 00:52:05 +0800
Hui Su <sh_def@163.com> wrote:
> The bdi_dev_name() returns a char [64], and
> the __entry->name is a char [32].
>
> It maybe dangerous to TP_printk("%s", __entry->name)
> after the strncpy().
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
This should go through the tree that has the code that uses these
tracepoints.
-- Steve
>
> Signed-off-by: Hui Su <sh_def@163.com>
> ---
> include/trace/events/writeback.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/trace/events/writeback.h b/include/trace/events/writeback.h
> index e7cbccc7c14c..57d795365987 100644
> --- a/include/trace/events/writeback.h
> +++ b/include/trace/events/writeback.h
> @@ -190,7 +190,7 @@ TRACE_EVENT(inode_foreign_history,
> ),
>
> TP_fast_assign(
> - strncpy(__entry->name, bdi_dev_name(inode_to_bdi(inode)), 32);
> + strscpy_pad(__entry->name, bdi_dev_name(inode_to_bdi(inode)), 32);
> __entry->ino = inode->i_ino;
> __entry->cgroup_ino = __trace_wbc_assign_cgroup(wbc);
> __entry->history = history;
> @@ -219,7 +219,7 @@ TRACE_EVENT(inode_switch_wbs,
> ),
>
> TP_fast_assign(
> - strncpy(__entry->name, bdi_dev_name(old_wb->bdi), 32);
> + strscpy_pad(__entry->name, bdi_dev_name(old_wb->bdi), 32);
> __entry->ino = inode->i_ino;
> __entry->old_cgroup_ino = __trace_wb_assign_cgroup(old_wb);
> __entry->new_cgroup_ino = __trace_wb_assign_cgroup(new_wb);
> @@ -252,7 +252,7 @@ TRACE_EVENT(track_foreign_dirty,
> struct address_space *mapping = page_mapping(page);
> struct inode *inode = mapping ? mapping->host : NULL;
>
> - strncpy(__entry->name, bdi_dev_name(wb->bdi), 32);
> + strscpy_pad(__entry->name, bdi_dev_name(wb->bdi), 32);
> __entry->bdi_id = wb->bdi->id;
> __entry->ino = inode ? inode->i_ino : 0;
> __entry->memcg_id = wb->memcg_css->id;
> @@ -285,7 +285,7 @@ TRACE_EVENT(flush_foreign,
> ),
>
> TP_fast_assign(
> - strncpy(__entry->name, bdi_dev_name(wb->bdi), 32);
> + strscpy_pad(__entry->name, bdi_dev_name(wb->bdi), 32);
> __entry->cgroup_ino = __trace_wb_assign_cgroup(wb);
> __entry->frn_bdi_id = frn_bdi_id;
> __entry->frn_memcg_id = frn_memcg_id;
next parent reply other threads:[~2020-11-24 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201124165205.GA23937@rlk>
2020-11-24 17:05 ` Steven Rostedt [this message]
2020-11-24 17:09 ` Tejun Heo
2020-11-25 12:05 ` Jan Kara
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=20201124120523.34a59eed@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=sh_def@163.com \
--cc=tj@kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®