From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BCBB9C433EF for ; Fri, 24 Jun 2022 23:08:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231684AbiFXXI0 (ORCPT ); Fri, 24 Jun 2022 19:08:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42058 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231516AbiFXXIZ (ORCPT ); Fri, 24 Jun 2022 19:08:25 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E366B46CB0 for ; Fri, 24 Jun 2022 16:08:23 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 92AA0B82CE5 for ; Fri, 24 Jun 2022 23:08:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F1DBBC34114; Fri, 24 Jun 2022 23:08:20 +0000 (UTC) Date: Fri, 24 Jun 2022 19:08:19 -0400 From: Steven Rostedt To: Chuck Lever III Cc: LKML Subject: Re: possible trace_printk() bug in v5.19-rc1 Message-ID: <20220624190819.59df11d3@rorschach.local.home> In-Reply-To: <355D2478-33D3-4046-8422-E512F42C51BC@oracle.com> References: <20220616113400.15335d91@gandalf.local.home> <20220617155019.373adda7@gandalf.local.home> <3BAD2CD9-3A34-4140-A28C-0FE798B83C41@oracle.com> <355D2478-33D3-4046-8422-E512F42C51BC@oracle.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Jun 2022 00:57:23 +0000 Chuck Lever III wrote: > > Yes, I'm sure. I just checked out v5.18 and built it with the > > same CONFIG. trace_printk() on that kernel generates function > > names as expected. > > I moved my development work to another system, and bisected. The > result: > > 91fb02f31505 ("module: Move kallsyms support into a separate file") Hmm, right below that it says: "No functional change." I'm guessing it may not be as reliably reproducible. And is this an issue with trace-cmd output or reading the trace file? -- Steve