From: Li Zefan <lizf@cn.fujitsu.com>
To: mingo@redhat.com
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, tzanussi@gmail.com,
a.p.zijlstra@chello.nl, fweisbec@gmail.com, rostedt@goodmis.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/core] tracing/events: fix concurrent access to ftrace_events list
Date: Thu, 07 May 2009 15:11:15 +0800 [thread overview]
Message-ID: <4A028993.7020509@cn.fujitsu.com> (raw)
In-Reply-To: <tip-20c8928abe70e204bd077ab6cfe23002d7788983@git.kernel.org>
tip-bot for Li Zefan wrote:
> Commit-ID: 20c8928abe70e204bd077ab6cfe23002d7788983
> Gitweb: http://git.kernel.org/tip/20c8928abe70e204bd077ab6cfe23002d7788983
> Author: Li Zefan <lizf@cn.fujitsu.com>
> AuthorDate: Wed, 6 May 2009 10:33:45 +0800
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Wed, 6 May 2009 10:38:19 +0200
>
> tracing/events: fix concurrent access to ftrace_events list
>
There is a deadlock in this patch, and I sent out a v2 patch and
expected it to be applied:
http://lkml.org/lkml/2009/5/6/26
Below is a fix on top of this patch. Sorry for my carelessness.
=========
From: Li Zefan <lizf@cn.fujitsu.com>
Subject: [PATCH] tracing/events: fix deadlock on event_mutex
In filter_add_subsystem_pred() we should release event_mutex before
calling filter_free_subsystem_preds(), since both functions hold
event_mutex.
[ Impact: fix deadlock when writing invalid pred into subsystem filter ]
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
kernel/trace/trace_events_filter.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
index 8c62e5b..85ad6a8 100644
--- a/kernel/trace/trace_events_filter.c
+++ b/kernel/trace/trace_events_filter.c
@@ -636,14 +636,15 @@ static int filter_add_subsystem_pred(struct filter_parse_state *ps,
err = filter_add_pred(ps, call, pred);
if (err) {
+ mutex_unlock(&event_mutex);
filter_free_subsystem_preds(system);
parse_error(ps, FILT_ERR_BAD_SUBSYS_FILTER, 0);
- break;
+ goto out;
}
replace_filter_string(call->filter, filter_string);
}
mutex_unlock(&event_mutex);
-
+out:
return err;
}
--
1.5.4.rc3
next prev parent reply other threads:[~2009-05-07 7:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 2:32 [PATCH 1/4] tracing/events: don't say hi when loading the trace event sample Li Zefan
2009-05-06 2:32 ` [PATCH 2/4] tracing/events: make SAMPLE_TRACE_EVENTS default to n Li Zefan
2009-05-06 12:19 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-05-06 2:33 ` [PATCH 3/4] tracing/events: fix memory leak when unloading module Li Zefan
2009-05-06 2:43 ` Steven Rostedt
2009-05-06 12:19 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-05-06 2:33 ` [PATCH 4/4] tracing/events: fix concurrent access to ftrace_events list Li Zefan
2009-05-06 5:27 ` Frederic Weisbecker
2009-05-06 8:40 ` Ingo Molnar
2009-05-06 5:30 ` [PATCH v2] " Li Zefan
2009-05-06 12:19 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-05-07 7:11 ` Li Zefan [this message]
2009-05-07 8:09 ` Ingo Molnar
2009-05-07 9:20 ` [tip:tracing/core] tracing/events: fix concurrent access to ftrace_events list, fix tip-bot for Li Zefan
2009-05-06 2:41 ` [PATCH 1/4] tracing/events: don't say hi when loading the trace event sample Steven Rostedt
2009-05-06 12:19 ` [tip:tracing/core] " tip-bot for Li Zefan
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=4A028993.7020509@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tzanussi@gmail.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