From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 7/8] tracing/filters: Fix MATCH_FULL filter matching for PTR_STRING
Date: Thu, 14 Jan 2010 22:57:33 -0500 [thread overview]
Message-ID: <20100115035853.910723642@goodmis.org> (raw)
In-Reply-To: 20100115035726.462940848@goodmis.org
[-- Attachment #1: 0007-tracing-filters-Fix-MATCH_FULL-filter-matching-for-P.patch --]
[-- Type: text/plain, Size: 1780 bytes --]
From: Li Zefan <lizf@cn.fujitsu.com>
MATCH_FULL matching for PTR_STRING is not working correctly:
# echo 'func == vt' > events/bkl/lock_kernel/filter
# echo 1 > events/bkl/lock_kernel/enable
...
# cat trace
Xorg-1484 [000] 1973.392586: lock_kernel: ... func=vt_ioctl()
gpm-1402 [001] 1974.027740: lock_kernel: ... func=vt_ioctl()
We should pass to regex.match(..., len) the length (including '\0')
of the source string instead of the length of the pattern string.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4B4E8763.5070707@cn.fujitsu.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/trace_events_filter.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
index f364b08..60c2a4e 100644
--- a/kernel/trace/trace_events_filter.c
+++ b/kernel/trace/trace_events_filter.c
@@ -211,8 +211,9 @@ static int filter_pred_pchar(struct filter_pred *pred, void *event,
{
char **addr = (char **)(event + pred->offset);
int cmp, match;
+ int len = strlen(*addr) + 1; /* including tailing '\0' */
- cmp = pred->regex.match(*addr, &pred->regex, pred->regex.field_len);
+ cmp = pred->regex.match(*addr, &pred->regex, len);
match = cmp ^ pred->not;
@@ -782,10 +783,8 @@ static int filter_add_pred(struct filter_parse_state *ps,
pred->regex.field_len = field->size;
} else if (field->filter_type == FILTER_DYN_STRING)
fn = filter_pred_strloc;
- else {
+ else
fn = filter_pred_pchar;
- pred->regex.field_len = strlen(pred->regex.pattern);
- }
} else {
if (field->is_signed)
ret = strict_strtoll(pred->regex.pattern, 0, &val);
--
1.6.5
next prev parent reply other threads:[~2010-01-15 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 3:57 [PATCH 0/8][GIT PULL][v2.6.33] tracing: fixes Steven Rostedt
2010-01-15 3:57 ` [PATCH 1/8] tracing/x86: Derive arch from bits argument in recordmcount.pl Steven Rostedt
2010-01-15 3:57 ` [PATCH 2/8] ftrace: Fix MATCH_END_ONLY function filter Steven Rostedt
2010-01-15 3:57 ` [PATCH 3/8] tracing/filters: Fix MATCH_FRONT_ONLY filter matching Steven Rostedt
2010-01-15 3:57 ` [PATCH 4/8] tracing/filters: Fix MATCH_END_ONLY " Steven Rostedt
2010-01-15 3:57 ` [PATCH 5/8] lib: Introduce strnstr() Steven Rostedt
2010-01-15 3:57 ` [PATCH 6/8] tracing/filters: Fix MATCH_MIDDLE_ONLY filter matching Steven Rostedt
2010-01-15 3:57 ` Steven Rostedt [this message]
2010-01-15 3:57 ` [PATCH 8/8] tracing/filters: Add comment for match callbacks Steven Rostedt
2010-01-16 6:56 ` [PATCH 0/8][GIT PULL][v2.6.33] tracing: fixes Ingo Molnar
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=20100115035853.910723642@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
/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