From: Steven Rostedt <rostedt@goodmis.org>
To: 王贇 <yun.wang@linux.alibaba.com>
Cc: Ingo Molnar <mingo@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [RESEND PATCH v2] trace: prevent preemption in perf_ftrace_function_call()
Date: Fri, 8 Oct 2021 20:03:28 -0400 [thread overview]
Message-ID: <20211008200328.5b88422d@oasis.local.home> (raw)
In-Reply-To: <eafba880-c1ae-2b99-c11e-d5041a2f6c3e@linux.alibaba.com>
On Tue, 28 Sep 2021 11:12:24 +0800
王贇 <yun.wang@linux.alibaba.com> wrote:
> With CONFIG_DEBUG_PREEMPT we observed reports like:
>
> BUG: using smp_processor_id() in preemptible
> caller is perf_ftrace_function_call+0x6f/0x2e0
> CPU: 1 PID: 680 Comm: a.out Not tainted
> Call Trace:
> <TASK>
> dump_stack_lvl+0x8d/0xcf
> check_preemption_disabled+0x104/0x110
> ? optimize_nops.isra.7+0x230/0x230
> ? text_poke_bp_batch+0x9f/0x310
> perf_ftrace_function_call+0x6f/0x2e0
> ...
It would be useful to see the full backtrace, to know how this
happened. Please do not shorten back traces.
-- Steve
> __text_poke+0x5/0x620
> text_poke_bp_batch+0x9f/0x310
>
> This telling us the CPU could be changed after task is preempted, and
> the checking on CPU before preemption will be invalid.
>
> This patch just turn off preemption in perf_ftrace_function_call()
> to prevent CPU changing.
>
> Reported-by: Abaci <abaci@linux.alibaba.com>
> Signed-off-by: Michael Wang <yun.wang@linux.alibaba.com>
> ---
> kernel/trace/trace_event_perf.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> index 6aed10e..dcbefdf 100644
> --- a/kernel/trace/trace_event_perf.c
> +++ b/kernel/trace/trace_event_perf.c
> @@ -441,12 +441,19 @@ void perf_trace_buf_update(void *record, u16 type)
> if (!rcu_is_watching())
> return;
>
> + /*
> + * Prevent CPU changing from now on. rcu must
> + * be in watching if the task was migrated and
> + * scheduled.
> + */
> + preempt_disable_notrace();
> +
> if ((unsigned long)ops->private != smp_processor_id())
> - return;
> + goto out;
>
> bit = ftrace_test_recursion_trylock(ip, parent_ip);
> if (bit < 0)
> - return;
> + goto out;
>
> event = container_of(ops, struct perf_event, ftrace_ops);
>
> @@ -468,16 +475,18 @@ void perf_trace_buf_update(void *record, u16 type)
>
> entry = perf_trace_buf_alloc(ENTRY_SIZE, NULL, &rctx);
> if (!entry)
> - goto out;
> + goto unlock;
>
> entry->ip = ip;
> entry->parent_ip = parent_ip;
> perf_trace_buf_submit(entry, ENTRY_SIZE, rctx, TRACE_FN,
> 1, ®s, &head, NULL);
>
> -out:
> +unlock:
> ftrace_test_recursion_unlock(bit);
> #undef ENTRY_SIZE
> +out:
> + preempt_enable_notrace();
> }
>
> static int perf_ftrace_function_register(struct perf_event *event)
next prev parent reply other threads:[~2021-10-09 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 3:12 [RESEND PATCH v2] trace: prevent preemption in perf_ftrace_function_call() 王贇
2021-10-09 0:03 ` Steven Rostedt [this message]
2021-10-11 2:38 ` 王贇
2021-10-11 8:32 ` Peter Zijlstra
2021-10-11 8:48 ` Peter Zijlstra
2021-10-11 9:39 ` 王贇
2021-10-11 14:45 ` Peter Zijlstra
2021-10-12 5:51 ` 王贇
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=20211008200328.5b88422d@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yun.wang@linux.alibaba.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