From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752600AbcF1Vuf (ORCPT ); Tue, 28 Jun 2016 17:50:35 -0400 Received: from mail-wm0-f50.google.com ([74.125.82.50]:35142 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752486AbcF1Vub (ORCPT ); Tue, 28 Jun 2016 17:50:31 -0400 From: Rasmus Villemoes To: Steven Rostedt Cc: Jiri Olsa , Lai Jiangshan , lkml , Frederic Weisbecker Subject: Re: [RFC/PATCH] lib/vsprintf: Add support to store cpumask Organization: D03 References: <1467128075-10841-1-git-send-email-jolsa@kernel.org> <20160628122608.0ea291b2@gandalf.local.home> <878txpi066.fsf@rasmusvillemoes.dk> <20160628155614.1cad283a@gandalf.local.home> X-Hashcash: 1:20:160628:rostedt@goodmis.org::kRfOXQXFsqUYfKbW:00000000000000000000000000000000000000000011Zm X-Hashcash: 1:20:160628:linux-kernel@vger.kernel.org::pXz9ifqXu2haIzm8:0000000000000000000000000000000001aPJ X-Hashcash: 1:20:160628:laijs@cn.fujitsu.com::G9zYKX7QbSpoSGZT:000000000000000000000000000000000000000001lTb X-Hashcash: 1:20:160628:fweisbec@gmail.com::geKjVPm6oVxaYqci:00000000000000000000000000000000000000000001hjI X-Hashcash: 1:20:160628:jolsa@kernel.org::xcBd9Gd0cxjIKbe7:03o/s Date: Tue, 28 Jun 2016 23:50:27 +0200 In-Reply-To: <20160628155614.1cad283a@gandalf.local.home> (Steven Rostedt's message of "Tue, 28 Jun 2016 15:56:14 -0400") Message-ID: <87mvm5gezg.fsf@rasmusvillemoes.dk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 28 2016, Steven Rostedt wrote: > But people don't usually run "make smatch" on debug kernels. > trace_printk() currently is not allowed to be used in the kernel. When > it is used, a big ugly banner is posted on boot up saying that the > kernel is in "debug mode" and is "unstable" (even though it isn't) just > to scare people enough to never compile with a trace_printk() in their > code. If they need a permanent trace_printk() then they need to use > tracepoints. But don't tracepoints also pass through vbin_printf? IOW, are there no print-like function calls in the kernel where a static checker warning for %pX would be worthwhile? Rasmus