Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3046122pxb; Tue, 19 Jan 2021 12:16:33 -0800 (PST) X-Google-Smtp-Source: ABdhPJyNsw9kQijdSl6VsavTqrYPoAGHwS7nwyIc/LzSlsJGGbQwNDKXIbdzkXYu7JduvjzwqulC X-Received: by 2002:a17:907:a06f:: with SMTP id ia15mr4099343ejc.328.1611087393065; Tue, 19 Jan 2021 12:16:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611087393; cv=none; d=google.com; s=arc-20160816; b=zdc8bEaplh02ojVybcofjnnhA/uq33bp8kbBDW+SThgAhuDmy0H8IodT66sw4FTkcs GMUwGN5TmZVtBPefsjWFpLK/QCOi4CW3dr0YDk5VFx/TE9MCxtT2vtmqt7rQ4hRs2rG5 l05Z0z3M2W/0zttCdoEfQEOInLm0Ap0lbXkJeGUphpPec/OHJUcKMYgKon7dGwEQkx7I wTD1VHe0SvkojH/DiIBT/08LPHyF9R6VXeTMWdn9conJU3Na64+Q94C7wpSWhCZTNinJ qtnrXW6WSg3LeCLjy95RfDsB3aJgADc3iGNlanZiCdSzUxa5D+dfr4HaKQRKPApWfHRf X7qw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=EOBENJuT7H4mUe75KbNGNoiexKO1J1bpJaqXrW+Kn4Y=; b=BRYdaxblN/AhpF2SeRc4s0QCHxufvwX0z4qbi6OjcxwJMatZo6boWI8uLozmN0nT6s 2CWIIwu46hLjev54WhoXzotIiQdmk7/kKkoALz8axZTWbFKwGy/2PU1HSY11pjFPtKCK nsqGzk+L87RSj4YdzTwtYmMaAlHL8+l7tSVGwdE2U5Y6j59xIo/+KPx2DaWsSq7efPFT wcSed4jxq7jJ19HPi560uP8/LP+jkSpwMTUX5Yu5+mAAzcHETb96KVXR/has871ZqyQm DSgqhq9ce6iHjpLjzIjc9psotpdpSgoYshF1Gp9E2Lb8Ncv1Nv+ADnbz1KkKZzq5bRrT bstQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y17si10121190edi.83.2021.01.19.12.16.05; Tue, 19 Jan 2021 12:16:33 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387973AbhASUMk (ORCPT + 99 others); Tue, 19 Jan 2021 15:12:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:53978 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391385AbhASUL2 (ORCPT ); Tue, 19 Jan 2021 15:11:28 -0500 Received: from gandalf.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 C211B23107; Tue, 19 Jan 2021 20:10:46 +0000 (UTC) Date: Tue, 19 Jan 2021 15:10:45 -0500 From: Steven Rostedt To: Timur Tabi Cc: Kees Cook , Matthew Wilcox , Sergey Senozhatsky , Andrew Morton , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, Petr Mladek , roman.fietze@magna.com, John Ogness , linux-mm@kvack.org, Akinobu Mita Subject: Re: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps Message-ID: <20210119151045.15c1fee3@gandalf.local.home> In-Reply-To: <29122c86-bfea-2f25-d111-00641cc660ba@kernel.org> References: <20210116220950.47078-1-timur@kernel.org> <20210118182635.GD2260413@casper.infradead.org> <20210119014725.GH2260413@casper.infradead.org> <202101191135.A78A570@keescook> <29122c86-bfea-2f25-d111-00641cc660ba@kernel.org> 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 Tue, 19 Jan 2021 13:55:29 -0600 Timur Tabi wrote: > > case DUMP_PREFIX_ADDRESS: > > printk("%s%s%p: %s\n", > > - level, prefix_str, ptr + i, linebuf); > > + level, prefix_str, addr + i, linebuf); > > Well, this is better than nothing, but not by much. Again, as long as > %px exists for printk(), I just cannot understand any resistance to > allowing it in print_hex_dump(). > > Frankly, I think this patch and my patch should both be added. During > debugging, it's very difficult if not impossible to work with hashed > addresses. I use print_hex_dump() with an unhashed address all the > time, either by applying my patch to my own kernel or just replacing the > %p with %px. I'm curious, what is the result if you replaced %p with %pS? That way you get a kallsyms offset version of the output, which could still be very useful depending on what you are dumping. -- Steve