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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 395F4C433E0 for ; Thu, 25 Feb 2021 02:03:09 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 8CCA664ECF for ; Thu, 25 Feb 2021 02:03:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8CCA664ECF Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 022D16B006E; Wed, 24 Feb 2021 21:03:08 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EEE796B0070; Wed, 24 Feb 2021 21:03:07 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DB5816B0071; Wed, 24 Feb 2021 21:03:07 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0199.hostedemail.com [216.40.44.199]) by kanga.kvack.org (Postfix) with ESMTP id C184B6B006E for ; Wed, 24 Feb 2021 21:03:07 -0500 (EST) Received: from smtpin30.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 90426FB51 for ; Thu, 25 Feb 2021 02:03:07 +0000 (UTC) X-FDA: 77855142414.30.272EE6F Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf14.hostedemail.com (Postfix) with ESMTP id C17C0C0007C3 for ; Thu, 25 Feb 2021 02:02:59 +0000 (UTC) Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E415964ECB; Thu, 25 Feb 2021 02:03:04 +0000 (UTC) Date: Wed, 24 Feb 2021 21:03:02 -0500 From: Steven Rostedt To: Linus Torvalds Cc: Andrew Morton , Christoph Lameter , Joonsoo Kim , jian.w.wen@oracle.com, Linux-MM , mm-commits@vger.kernel.org, Paul McKenney , Pekka Enberg , David Rientjes Subject: Re: [patch 014/173] mm, tracing: record slab name for kmem_cache_free() Message-ID: <20210224210302.0e0a196a@oasis.local.home> In-Reply-To: References: <20210224115824.1e289a6895087f10c41dd8d6@linux-foundation.org> <20210224200055.U7Xz47kX5%akpm@linux-foundation.org> <20210224203708.4489755a@oasis.local.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: C17C0C0007C3 X-Stat-Signature: p1khh68fwy1wezwnu5f58y54at14iah8 Received-SPF: none (kernel.org>: No applicable sender policy available) receiver=imf14; identity=mailfrom; envelope-from=""; helo=mail.kernel.org; client-ip=198.145.29.99 X-HE-DKIM-Result: none/none X-HE-Tag: 1614218579-595631 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, 24 Feb 2021 17:51:46 -0800 Linus Torvalds wrote: > On Wed, Feb 24, 2021 at 5:37 PM Steven Rostedt wrote: > > > > Please do not apply this patch as is, it is very buggy! > > Sadly, it's already there and pushed out. I try to wait a few hours > (sometimes overnight) with Andrew's series before pushing things out > in order to catch comments like this, but this one came too late. I try to look at patches like this for these very mistakes. I don't seem to be Cc'd on the original patch, and this looks to be the first time I've seen this patch. I should update my lkml filter to send me any patches that touch include/trace/ code or has TRACE_EVENT in it, and forward it to my inbox if I'm not already on the Cc. > > I can obviously revert, but if the fix is the two-liner you outlined, > perhaps that is better? Mind sending it as a patch (or just putting it > in your tracing tree)? Or Jacob? A tested patch along the lines that > Steven outlined? I'm done for the night, but if nobody does anything by tomorrow, I can write up a quick fix in a few minutes. I prefer the original author to do it, just so they get into the habit of understanding strings in events. But even though it's very buggy, it wont break anything unless people really try to. The breakage would require enabling the event, then doing something that would free a slab and its name, then reading the trace file that has the events. In other words, the risk is low, but something you don't want on a production system. I don't see this breaking current mainline testing, so its not urgent to get fixed immediately. -- Steve