From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
zhengyejian1@huawei.com, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing: Simplify and fix "buffered event" synchronization
Date: Fri, 1 Dec 2023 09:46:39 -0500 [thread overview]
Message-ID: <20231201094639.03a1913c@gandalf.local.home> (raw)
In-Reply-To: <d404113e-4ffe-4e9c-ab45-1b076c1f498c@suse.com>
On Fri, 1 Dec 2023 15:17:35 +0100
Petr Pavlu <petr.pavlu@suse.com> wrote:
> Ok, keeping the current approach, my plan for v2 is to prepare the
> following patches:
>
> * Fix for the missing increment+decrement of trace_buffered_event_cnt
> on the current CPU in trace_buffered_event_disable().
>
> Replace smp_call_function_many() with on_each_cpu_mask() in
> trace_buffered_event_disable(). The on_each_cpu_mask() function has
> also an advantage that it itself disables preemption so doing that can
> be then removed from trace_buffered_event_disable().
OK.
>
> * Fix the potential race between trace_buffered_event_enable() and
> trace_event_buffer_lock_reserve() where the latter might already see
> a valid trace_buffered_event pointer but not all initialization yet.
>
> I think this might be actually best to address by using the same
> maintenance exclusion as is implemented in
> trace_buffered_event_disable(). It would make both maintenance
> operations consistent but for the cost of making the enable operation
> somewhat slower.
I wouldn't do them the same just to make them consistent. I think the
smp_wmb() is sufficient. Don't you think?
>
> * Fix the WARN_ON_ONCE(!trace_buffered_event_ref) issued in
> trace_buffered_event_disable() when trace_buffered_event_enable()
> previously fails.
>
> Add a variable/flag tracking whether trace_buffered_event is currently
> allocated and use that for driving if a new allocation needs to be
> done when trace_buffered_event_enable() is called, or the buffers
> should be really freed when trace_buffered_event_disable() is invoked.
>
> Not sure if the mentioned alternative of leaving trace_buffered_event
> partially initialized on failure is preferred instead.
I do not really have a preference for either solution. They both are bad if
it happens ;-)
>
> * Fix the potential race between trace_buffered_event_disable() and
> trace_event_buffer_lock_reserve() where the latter might still grab
> a pointer from trace_buffered_event that is being freed.
>
> Replace smp_wmb() with synchronize_rcu() in
> trace_buffered_event_disable().
Sounds good.
Thanks!
-- Steve
next prev parent reply other threads:[~2023-12-01 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:12 [PATCH 0/2] tracing: Simplify and fix "buffered event" synchronization Petr Pavlu
2023-11-27 15:12 ` [PATCH 1/2] " Petr Pavlu
2023-11-27 17:41 ` Steven Rostedt
2023-11-28 15:05 ` Petr Pavlu
2023-11-28 15:27 ` Steven Rostedt
2023-11-29 9:22 ` Petr Pavlu
2023-11-29 14:58 ` Steven Rostedt
2023-12-01 14:17 ` Petr Pavlu
2023-12-01 14:46 ` Steven Rostedt [this message]
2023-12-05 16:16 ` Petr Pavlu
2023-11-27 15:12 ` [PATCH 2/2] tracing: Disable events in reverse order of their enable operation Petr Pavlu
2023-11-27 17:58 ` Steven Rostedt
2023-11-28 15:06 ` Petr Pavlu
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=20231201094639.03a1913c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=petr.pavlu@suse.com \
--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