diff options
| author |   Zheng Yejian <zhengyejian1@huawei.com> | 2022-10-11 12:03:52 +0000 |
|---|---|---|
| committer |   Steven Rostedt (Google) <rostedt@goodmis.org> | 2022-10-12 07:05:47 -0400 |
| commit | 30f7d1cac2aab8fec560a388ad31ca5e5d04a822 (patch) | |
| tree | cc10eac59bb68a30e9bec297c6ddfc12150fc6ce /kernel/trace/ring_buffer.c | |
| parent | ftrace: Create separate entry in MAINTAINERS for function hooks (diff) | |
| download | linux-dev-30f7d1cac2aab8fec560a388ad31ca5e5d04a822.tar.xz linux-dev-30f7d1cac2aab8fec560a388ad31ca5e5d04a822.zip | |
ftrace: Fix char print issue in print_ip_ins()
When ftrace bug happened, following log shows every hex data in
problematic ip address:
actual: ffffffe8:6b:ffffffd9:01:21
But so many 'f's seem a little confusing, and that is because format
'%x' being used to print signed chars in array 'ins'. As suggested
by Joe, change to use format "%*phC" to print array 'ins'.
After this patch, the log is like:
actual: e8:6b:d9:01:21
Link: https://lkml.kernel.org/r/20221011120352.1878494-1-zhengyejian1@huawei.com
Fixes: 6c14133d2d3f ("ftrace: Do not blindly read the ip address in ftrace_bug()")
Suggested-by: Joe Perches <joe@perches.com>
Signed-off-by: Zheng Yejian <zhengyejian1@huawei.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/ring_buffer.c')
0 files changed, 0 insertions, 0 deletions