Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1301723 > unrolled thread

[PATCH 0/2] [GIT PULL] tracing: Some minor fixes

Started bySteven Rostedt <rostedt@goodmis.org>
First post2016-01-05 18:20 +0100
Last post2016-01-05 18:20 +0100
Articles 2 — 1 participant

Back to article view | Back to linux.kernel


Contents

  [PATCH 0/2] [GIT PULL] tracing: Some minor fixes Steven Rostedt <rostedt@goodmis.org> - 2016-01-05 18:20 +0100
    [PATCH 2/2] tracing: Fix setting of start_index in find_next() Steven Rostedt <rostedt@goodmis.org> - 2016-01-05 18:20 +0100

#1301723 — [PATCH 0/2] [GIT PULL] tracing: Some minor fixes

FromSteven Rostedt <rostedt@goodmis.org>
Date2016-01-05 18:20 +0100
Subject[PATCH 0/2] [GIT PULL] tracing: Some minor fixes
Message-ID<qNDr4-5S2-5@gated-at.bofh.it>
Linus,

Two more fixes.

 1. The recordmcount change had an output that used sprintf() (incorrectly)
    when it should have been a fprintf() to stderr.

 2. The printk_formats file could crash if someone added a trace_printk()
    in the core kernel, and also added one in a module. This does not
    affect production kernels. Only kernels where developers add trace_printk()
    for debugging can crash.

Please pull the latest trace-v4.4-rc4-3 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.4-rc4-3

Tag SHA1: 88d7ab59dbb2c2dd97158589e7c3b1b44cd792be
Head SHA1: f36d1be2930ede0a1947686e1126ffda5d5ee1bb


Colin Ian King (1):
      ftrace/scripts: Fix incorrect use of sprintf in recordmcount

Qiu Peiyang (1):
      tracing: Fix setting of start_index in find_next()

----
 kernel/trace/trace_printk.c | 1 +
 scripts/recordmcount.c      | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1301724 — [PATCH 2/2] tracing: Fix setting of start_index in find_next()

FromSteven Rostedt <rostedt@goodmis.org>
Date2016-01-05 18:20 +0100
Subject[PATCH 2/2] tracing: Fix setting of start_index in find_next()
Message-ID<qNDr4-5S2-7@gated-at.bofh.it>
In reply to#1301723
From: Qiu Peiyang <peiyangx.qiu@intel.com>

When we do cat /sys/kernel/debug/tracing/printk_formats, we hit kernel
panic at t_show.

general protection fault: 0000 [#1] PREEMPT SMP
CPU: 0 PID: 2957 Comm: sh Tainted: G W  O 3.14.55-x86_64-01062-gd4acdc7 #2
RIP: 0010:[<ffffffff811375b2>]
 [<ffffffff811375b2>] t_show+0x22/0xe0
RSP: 0000:ffff88002b4ebe80  EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000004
RDX: 0000000000000004 RSI: ffffffff81fd26a6 RDI: ffff880032f9f7b1
RBP: ffff88002b4ebe98 R08: 0000000000001000 R09: 000000000000ffec
R10: 0000000000000000 R11: 000000000000000f R12: ffff880004d9b6c0
R13: 7365725f6d706400 R14: ffff880004d9b6c0 R15: ffffffff82020570
FS:  0000000000000000(0000) GS:ffff88003aa00000(0063) knlGS:00000000f776bc40
CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f6c02ff0 CR3: 000000002c2b3000 CR4: 00000000001007f0
Call Trace:
 [<ffffffff811dc076>] seq_read+0x2f6/0x3e0
 [<ffffffff811b749b>] vfs_read+0x9b/0x160
 [<ffffffff811b7f69>] SyS_read+0x49/0xb0
 [<ffffffff81a3a4b9>] ia32_do_call+0x13/0x13
 ---[ end trace 5bd9eb630614861e ]---
Kernel panic - not syncing: Fatal exception

When the first time find_next calls find_next_mod_format, it should
iterate the trace_bprintk_fmt_list to find the first print format of
the module. However in current code, start_index is smaller than *pos
at first, and code will not iterate the list. Latter container_of will
get the wrong address with former v, which will cause mod_fmt be a
meaningless object and so is the returned mod_fmt->fmt.

This patch will fix it by correcting the start_index. After fixed,
when the first time calls find_next_mod_format, start_index will be
equal to *pos, and code will iterate the trace_bprintk_fmt_list to
get the right module printk format, so is the returned mod_fmt->fmt.

Link: http://lkml.kernel.org/r/5684B900.9000309@intel.com

Cc: stable@vger.kernel.org # 3.12+
Fixes: 102c9323c35a8 "tracing: Add __tracepoint_string() to export string pointers"
Signed-off-by: Qiu Peiyang <peiyangx.qiu@intel.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 kernel/trace/trace_printk.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/trace/trace_printk.c b/kernel/trace/trace_printk.c
index 1c2b28536feb..060df67dbdd1 100644
--- a/kernel/trace/trace_printk.c
+++ b/kernel/trace/trace_printk.c
@@ -273,6 +273,7 @@ static const char **find_next(void *v, loff_t *pos)
 	if (*pos < last_index + start_index)
 		return __start___tracepoint_str + (*pos - last_index);
 
+	start_index += last_index;
 	return find_next_mod_format(start_index, v, fmt, pos);
 }
 
-- 
2.6.2


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web