From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868AbcAERSN (ORCPT ); Tue, 5 Jan 2016 12:18:13 -0500 Received: from mail.kernel.org ([198.145.29.136]:47534 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751569AbcAERSL (ORCPT ); Tue, 5 Jan 2016 12:18:11 -0500 Message-Id: <20160105171715.485344115@goodmis.org> User-Agent: quilt/0.61-1 Date: Tue, 05 Jan 2016 12:17:15 -0500 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Linus Torvalds , Ingo Molnar , Andrew Morton Subject: [PATCH 0/2] [GIT PULL] tracing: Some minor fixes Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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(-)