From: Zheng Yejian <zhengyejian1@huawei.com>
To: Brian Foster <bfoster@redhat.com>, <linux-trace-kernel@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <rostedt@goodmis.org>
Subject: Re: [PATCH] tracing: zero the pipe cpumask on alloc to avoid spurious -EBUSY
Date: Thu, 31 Aug 2023 21:51:18 +0800 [thread overview]
Message-ID: <26f8fb43-6ea8-edc2-381d-3600fce261af@huawei.com> (raw)
In-Reply-To: <20230831125500.986862-1-bfoster@redhat.com>
On 2023/8/31 20:55, Brian Foster wrote:
> The pipe cpumask used to serialize opens between the main and percpu
> trace pipes is not zeroed or initialized. This can result in
> spurious -EBUSY returns if underlying memory is not fully zeroed.
> This has been observed by immediate failure to read the main
> trace_pipe file on an otherwise newly booted and idle system:
>
> # cat /sys/kernel/debug/tracing/trace_pipe
> cat: /sys/kernel/debug/tracing/trace_pipe: Device or resource busy
>
> Zero the allocation of pipe_cpumask to avoid the problem.
>
> Fixes: c2489bb7e6be ("tracing: Introduce pipe_cpumask to avoid race on trace_pipes")
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> Hi,
>
> I ran into this problem just recently on one of my test VMs immediately
> after updating to a v6.5 base. A revert of the aforementioned commit
> addressed the problem. I'm not terribly familiar with the tracing code,
> but on further inspection I noticed the cpumask doesn't appear to be
> initialized anywhere. I suppose this could alternatively do a
> cpumask_clear() or whatever after allocation, but either way this
> addresses the problem for me.
Yes, pipe_cpumask must be initialized.
--
Thanks,
Zheng Yejian
>
> Please CC on replies as I'm not subscribed to the list. Thanks.
>
> Brian
>
> 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 8e64aaad5361..2656ca3b9b39 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -9486,7 +9486,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;
> @@ -10431,7 +10431,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 */
next prev parent reply other threads:[~2023-08-31 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 12:55 [PATCH] tracing: zero the pipe cpumask on alloc to avoid spurious -EBUSY Brian Foster
2023-08-31 13:51 ` Zheng Yejian [this message]
2023-08-31 20:33 ` Steven Rostedt
2023-09-01 1:34 ` Zheng Yejian
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=26f8fb43-6ea8-edc2-381d-3600fce261af@huawei.com \
--to=zhengyejian1@huawei.com \
--cc=bfoster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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