From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: trace: use-after-free in hist_unreg_all
Date: Tue, 28 Jun 2016 19:01:46 -0500 [thread overview]
Message-ID: <57730FEA.7050102@linux.intel.com> (raw)
In-Reply-To: <20160628104309.4bbafced@gandalf.local.home>
Hi Steve,
On 06/28/2016 09:43 AM, Steven Rostedt wrote:
> On Tue, 28 Jun 2016 14:58:50 +0200
> Dmitry Vyukov <dvyukov@google.com> wrote:
>
>> Hello,
>>
>> While running tools/testing/selftests test suite with KASAN I hit the
>> following use-after-free report:
>>
>>
>>
>> ==================================================================
>> BUG: KASAN: use-after-free in hist_unreg_all+0x1a1/0x1d0 at addr
>> ffff880031632cc0
>> Read of size 8 by task ftracetest/7413
>> =============================================================================
>> BUG kmalloc-128 (Not tainted): kasan: bad access detected
>> -----------------------------------------------------------------------------
>
> Thanks for the report. Can you check if this patch fixes the issue?
>
> -- Steve
>
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index 0c05b8a99806..948adb4b6761 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -1699,9 +1699,9 @@ hist_enable_get_trigger_ops(char *cmd, char *param)
>
> static void hist_enable_unreg_all(struct trace_event_file *file)
This does fix the problem, if put on hist_unreg_all() instead of this ;-)
Actually, with that gone, I see another problem with the multihist test,
which I'm digging into now.
Actually, I should really run through my whole testsuite with KASAN
turned on...
Thanks for the initial patch, in any case.
Tom
> {
> - struct event_trigger_data *test;
> + struct event_trigger_data *test, *n;
>
> - list_for_each_entry_rcu(test, &file->triggers, list) {
> + list_for_each_entry_safe(test, n, &file->triggers, list) {
> if (test->cmd_ops->trigger_type == ETT_HIST_ENABLE) {
> list_del_rcu(&test->list);
> update_cond_flag(file);
>
next prev parent reply other threads:[~2016-06-29 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 12:58 trace: use-after-free in hist_unreg_all Dmitry Vyukov
2016-06-28 14:43 ` Steven Rostedt
2016-06-29 0:01 ` Tom Zanussi [this message]
2016-08-31 2:04 ` amanda4ray
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=57730FEA.7050102@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).