diff options
| author | Masami Hiramatsu <mhiramat@kernel.org> | 2019-05-07 22:56:02 +0900 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-05-08 12:15:11 -0400 |
| commit | 3dd1f7f24f8ceec00bbbc364c2ac3c893f0fdc4c (patch) | |
| tree | 52f84e3e554bd5259c4c12477aa528658b365c97 /fs | |
| parent | 489fe0096b19b664b8f3bed0fd604d617a229b5a (diff) | |
| download | linux-3dd1f7f24f8ceec00bbbc364c2ac3c893f0fdc4c.tar.gz linux-3dd1f7f24f8ceec00bbbc364c2ac3c893f0fdc4c.tar.bz2 linux-3dd1f7f24f8ceec00bbbc364c2ac3c893f0fdc4c.zip | |
tracing: probeevent: Fix to make the type of $comm string
Fix to make the type of $comm "string". If we set the other type to $comm
argument, it shows meaningless value or wrong data. Currently probe events
allow us to set string array type (e.g. ":string[2]"), or other digit types
like x8 on $comm. But since clearly $comm is just a string data, it should
not be fetched by other types including array.
Link: http://lkml.kernel.org/r/155723736241.9149.14582064184468574539.stgit@devnote2
Cc: Andreas Ziegler <andreas.ziegler@fau.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: stable@vger.kernel.org
Fixes: 533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions