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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 3C0FAC433E0 for ; Wed, 10 Feb 2021 16:59:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E9BF664E7E for ; Wed, 10 Feb 2021 16:59:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232421AbhBJQ6j (ORCPT ); Wed, 10 Feb 2021 11:58:39 -0500 Received: from mga06.intel.com ([134.134.136.31]:7976 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232903AbhBJQ6H (ORCPT ); Wed, 10 Feb 2021 11:58:07 -0500 IronPort-SDR: jtMW4iIy6IQgyN1+zdQZT2Ypa8twsbmJYPNdXZRYqopHnB30jc/JmLtcrZwhPM7mUZBgqt6tE6 4WsG8Ke3zqww== X-IronPort-AV: E=McAfee;i="6000,8403,9891"; a="243600272" X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="243600272" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2021 08:54:20 -0800 IronPort-SDR: YaHAI6bJQoUB7zMRBVuvHxXrWC1N8RXcKfsBSKreSHGJXC5Jz648w2uzLzbxNb4NTkGf52nZ2R SwwyG1s397/A== X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="586375276" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2021 08:54:15 -0800 Received: from andy by smile with local (Exim 4.94) (envelope-from ) id 1l9skl-003m9n-6t; Wed, 10 Feb 2021 18:54:11 +0200 Date: Wed, 10 Feb 2021 18:54:11 +0200 From: Andy Shevchenko To: Tetsuo Handa Cc: Steven Rostedt , Timur Tabi , Petr Mladek , Sergey Senozhatsky , Vlastimil Babka , Matthew Wilcox , akpm@linux-foundation.org, Linus Torvalds , roman.fietze@magna.com, Kees Cook , John Ogness , akinobu.mita@gmail.com, glider@google.com, Andrey Konovalov , Marco Elver , Rasmus Villemoes , Pavel Machek , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 0/3][RESEND] add support for never printing hashed addresses Message-ID: References: <20210210051814.845713-1-timur@kernel.org> <6da0be5a-7cb0-4943-e61f-7c3275e60cb6@i-love.sakura.ne.jp> <20210210111836.2468f10a@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 11, 2021 at 01:39:41AM +0900, Tetsuo Handa wrote: > On 2021/02/11 1:18, Steven Rostedt wrote: > > The point of this exercise is to be able to debug the *same* kernel that > > someone is having issues with. And this is to facilitate that debugging. > > That's too difficult to use. If a problem is not reproducible, we will have > no choice but always specify "never hash pointers" command line option. If a > problem is reproducible, we can rebuild that kernel with "never hash pointers" > config option turned on. I think what you are targeting is something like dynamic debug approach where you can choose which prints to enable/disable and what enable/disable in them. In that case you specifically apply a command line option and enable only files / lines in the files. -- With Best Regards, Andy Shevchenko