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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160105171715.485344115@goodmis.org>
Date:	Tue, 05 Jan 2016 12:17:15 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: Some minor fixes


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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/