Messages in this thread | | | Date | Tue, 24 Nov 2020 12:09:02 -0500 | From | Tejun Heo <> | Subject | Re: [PATCH] trace: fix potenial dangerous pointer |
| |
On Tue, Nov 24, 2020 at 12:05:23PM -0500, Steven Rostedt wrote: > 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.
Acked-by: Tejun Heo <tj@kernel.org>
Andrew, can you please route this one?
Thanks.
-- tejun
| |