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=-7.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 9733AC433DB for ; Tue, 26 Jan 2021 18:13:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4E11520793 for ; Tue, 26 Jan 2021 18:13:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2394248AbhAZSM7 (ORCPT ); Tue, 26 Jan 2021 13:12:59 -0500 Received: from mail.kernel.org ([198.145.29.99]:36982 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731480AbhAZRaq (ORCPT ); Tue, 26 Jan 2021 12:30:46 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 8339120731; Tue, 26 Jan 2021 17:30:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1611682206; bh=vSXKKnE/bLBTYW50gSYHtVaoA4CgDmimolqgLlfelRM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=sXbwAGTP/5Sqws5TJzQGuE1z+JnSDvWUtL6CfygmHovUFWdQGET5UPBfhvBoS8Psz 8seaHA75ynp+t3LmsQqoAkpVMjpa880FbamQVZeYQTIvkjryWnOMjOjd4R4Uvrj1gc 7yzfl7OVkD10bFQAGQGhe4PL9/DASguadRCPKefjJh5BrG8Hc9q7DSC5ROO9nxnCdk Z+vc73h7zLBE8avPqVER5Ao3NBva98fLvu1ArPKm7zhbTw2Sx/fsXKyBuIaPqj4t6p Et9RMTdBZ7sbjOc8oWuDaEpBT4wZkQwGbmenccb7BkKDmVPhghWx/Fij4yYpS3xn8R u3Bi6CrxViw/A== Subject: Re: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps To: Vlastimil Babka , Sergey Senozhatsky , Matthew Wilcox Cc: Andrew Morton , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, Petr Mladek , roman.fietze@magna.com, keescook@chromium.org, Steven Rostedt , John Ogness , linux-mm@kvack.org, Akinobu Mita References: <20210116220950.47078-1-timur@kernel.org> <20210118182635.GD2260413@casper.infradead.org> <20210119014725.GH2260413@casper.infradead.org> <09c70d6b-c989-ca23-7ee8-b404bb0490f0@suse.cz> <083dd940-60c1-4cc8-fc89-8815b253d5c5@suse.cz> From: Timur Tabi Message-ID: Date: Tue, 26 Jan 2021 11:30:02 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <083dd940-60c1-4cc8-fc89-8815b253d5c5@suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/26/21 11:14 AM, Vlastimil Babka wrote: > If it was a boot option, I would personally be for leaving hashing enabled by > default, with opt-in boot option to disable it. A boot option would solve all my problems. I wouldn't need to recompile the kernel, and it would apply to all variations of printk.