From: Steven Rostedt <rostedt@goodmis.org>
To: Prateek Sood <prsood@codeaurora.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
sramana@codeaurora.org, fweisbec@gmail.com, jolsa@redhat.com
Subject: Re: [PATCH] perf: fix use after free of perf_trace_buf
Date: Tue, 19 Mar 2019 09:31:22 -0400 [thread overview]
Message-ID: <20190319093122.70bfc751@gandalf.local.home> (raw)
In-Reply-To: <1552998060-5735-1-git-send-email-prsood@codeaurora.org>
On Tue, 19 Mar 2019 17:51:00 +0530
Prateek Sood <prsood@codeaurora.org> wrote:
> SyS_perf_event_open()
> free_event()
> _free_event()
> tp_perf_event_destroy()
> perf_trace_destroy()
> perf_trace_event_unreg() //free perf_trace_buf
>
> trace_cpu_frequency()
> perf_trace_cpu()
> perf_trace_buf_alloc() //access perf_trace_buf
>
> CPU0 CPU1
> perf_trace_event_unreg() perf_trace_cpu()
> head = (event_call->perf_events)
>
But here there's a:
tracepoint_synchronize_unregister();
Which is suppose to prevent this. Are you saying that the
tracepoint_synchronize_unregister() is broken?
-- Steve
> free_percpu(tp_event->perf_events)
> tp_event->perf_events = NULL
> --total_ref_count
> free_percpu(perf_trace_buf[i])
> perf_trace_buf[i] = NULL
>
> raw_data = perf_trace_buf[rctx]
> memset(raw_data)
>
> A potential race exists between access of perf_trace_buf from
> perf_trace_buf_alloc() and perf_trace_event_unreg(). This can
> result in perf_trace_buf[rctx] being NULL during access from memset()
> in perf_trace_buf_alloc().
>
next prev parent reply other threads:[~2019-03-19 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:47 [PATCH] perf: extend total_ref_count usage to protect perf_trace_buf access Prateek Sood
2019-03-18 15:02 ` Steven Rostedt
2019-03-18 15:15 ` Peter Zijlstra
2019-03-19 12:21 ` [PATCH] perf: fix use after free of perf_trace_buf Prateek Sood
2019-03-19 13:31 ` Steven Rostedt [this message]
2019-03-19 13:37 ` Jiri Olsa
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=20190319093122.70bfc751@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prsood@codeaurora.org \
--cc=sramana@codeaurora.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
all inboxes | Powered by JetHome®