tools lib traceevent: Fix bad force_token escape sequence
authorMichael Sartain <mikesart@fastmail.com>
Fri, 12 Jan 2018 00:47:42 +0000 (19:47 -0500)
committerArnaldo Carvalho de Melo <acme@redhat.com>
Wed, 17 Jan 2018 13:21:39 +0000 (10:21 -0300)
Older kernels have a bug that creates invalid symbols. event-parse.c
handles them by replacing them with a "%s" token. But the fix included
an extra backslash, and "\%s" was added incorrectly.

Signed-off-by: Michael Sartain <mikesart@fastmail.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/20180112004821.827168881@goodmis.org
Link: http://lkml.kernel.org/r/d320000d37c10ce0912851e1fb78d1e0c946bcd9.1497486273.git.mikesart@fastmail.com
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
tools/lib/traceevent/event-parse.c

index 7ce724fc054478c923605385fd00d8471de831e6..0bc1a6df8a27df58ff990d6de38ab5b929059616 100644 (file)
@@ -1094,7 +1094,7 @@ static enum event_type __read_token(char **tok)
                if (strcmp(*tok, "LOCAL_PR_FMT") == 0) {
                        free(*tok);
                        *tok = NULL;
-                       return force_token("\"\%s\" ", tok);
+                       return force_token("\"%s\" ", tok);
                } else if (strcmp(*tok, "STA_PR_FMT") == 0) {
                        free(*tok);
                        *tok = NULL;