linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Chuang Wang <nashuiliang@gmail.com>,
	stable@vger.kernel.org, Zheng Yejian <zhengyejian1@huawei.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH] tracing: Fix the unusable problem caused by non-empty pipe_cpumask
Date: Fri, 1 Sep 2023 21:26:07 -0400	[thread overview]
Message-ID: <20230901212607.1f8608de@gandalf.local.home> (raw)
In-Reply-To: <20230901230206.9bf0250291acd7bfbde46b53@kernel.org>

On Fri, 1 Sep 2023 23:02:06 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> On Fri,  1 Sep 2023 15:26:26 +0800
> Chuang Wang <nashuiliang@gmail.com> wrote:
> 
> > There is a problem in the linux-6.5 when I execute the following
> > command:
> > 
> >  $ perf ftrace -t irqsoff
> >  failed to open trace_pipe
> > 
> > At the same time, when I open this file, the same error occurs.
> > 
> > Therefore, after carefully looking at the code, the open function of
> > 'trace_pipe' returns -EBUSY in open_pipe_on_cpu() because no clearing
> > operation was performed when 'trace_array->pipe_cpumask' was allocated.
> > 
> > With this patch, Use zalloc_cpumask_var() to ensure that
> > 'trace_array->pipe_cpumask' is reset to 0 when allocated.  


Brian Foster beat you to it.

  https://lore.kernel.org/linux-trace-kernel/20230831125500.986862-1-bfoster@redhat.com


> 
> Good catch. This looks good to me.
> 
> Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 

Masami, I'll add your Reviewed-by to that commit.

Thanks!

-- Steve

> > 
> > Cc: stable@vger.kernel.org
> > Fixes: c2489bb7e6be ("tracing: Introduce pipe_cpumask to avoid race on trace_pipes")
> > Signed-off-by: Chuang Wang <nashuiliang@gmail.com>
> > ---
> >  kernel/trace/trace.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> > index d8233d34b5a0..c0b8a72f3466 100644
> > --- a/kernel/trace/trace.c
> > +++ b/kernel/trace/trace.c
> > @@ -9461,7 +9461,7 @@ static struct trace_array *trace_array_create(const char *name)
> >  	if (!alloc_cpumask_var(&tr->tracing_cpumask, GFP_KERNEL))
> >  		goto out_free_tr;
> >  
> > -	if (!alloc_cpumask_var(&tr->pipe_cpumask, GFP_KERNEL))
> > +	if (!zalloc_cpumask_var(&tr->pipe_cpumask, GFP_KERNEL))
> >  		goto out_free_tr;
> >  
> >  	tr->trace_flags = global_trace.trace_flags & ~ZEROED_TRACE_FLAGS;
> > @@ -10406,7 +10406,7 @@ __init static int tracer_alloc_buffers(void)
> >  	if (trace_create_savedcmd() < 0)
> >  		goto out_free_temp_buffer;
> >  
> > -	if (!alloc_cpumask_var(&global_trace.pipe_cpumask, GFP_KERNEL))
> > +	if (!zalloc_cpumask_var(&global_trace.pipe_cpumask, GFP_KERNEL))
> >  		goto out_free_savedcmd;
> >  
> >  	/* TODO: make the number of buffers hot pluggable with CPUS */
> > -- 
> > 2.39.2
> >   
> 
> 


      reply	other threads:[~2023-09-02  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  7:26 [PATCH] tracing: Fix the unusable problem caused by non-empty pipe_cpumask Chuang Wang
2023-09-01 14:02 ` Masami Hiramatsu
2023-09-02  1:26   ` Steven Rostedt [this message]

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=20230901212607.1f8608de@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bfoster@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=nashuiliang@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=zhengyejian1@huawei.com \
    /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).