From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752437AbdLGFiD (ORCPT ); Thu, 7 Dec 2017 00:38:03 -0500 Received: from mail-pf0-f178.google.com ([209.85.192.178]:39052 "EHLO mail-pf0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750803AbdLGFiB (ORCPT ); Thu, 7 Dec 2017 00:38:01 -0500 X-Google-Smtp-Source: AGs4zMZ/8z0gfv2gUkusvG8nHgi2o/z+WtyMFAKoCH2YIYDQZBql7r6GqDWxcHhLIUnl6UZflUQfEg== Date: Thu, 7 Dec 2017 14:37:55 +0900 From: Sergey Senozhatsky To: "Tobin C. Harding" Cc: Sergey Senozhatsky , Geert Uytterhoeven , Linus Torvalds , Randy Dunlap , David Laight , Kees Cook , "kernel-hardening@lists.openwall.com" , "Jason A. Donenfeld" , "Theodore Ts'o" , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Joe Perches , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon , Steven Rostedt , Chris Fries , Dave Weinstein , Daniel Micay , Djalal Harouni , Radim =?iso-8859-1?Q?Krcm=E1r?= , Linux Kernel Mailing List , Network Development , David Miller , Stephen Rothwell , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Andrew Morton Subject: Re: [PATCH V11 4/5] vsprintf: add printk specifier %px Message-ID: <20171207053755.GC6084@jagdpanzerIV> References: <324abe19f1ee4177911d2fc48899ac8a@AcuMS.aculab.com> <596c917e-3183-d80a-89d4-97e0eb5dc077@infradead.org> <20171206013657.GA479@jagdpanzerIV> <20171206084537.GA462@jagdpanzerIV> <20171207051711.GB2191@eros> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171207051711.GB2191@eros> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (12/07/17 16:17), Tobin C. Harding wrote: [..] > > hm, indeed. and !CONFIG_KALLSYMS config turns %pS/%ps > > into special_hex_number(). > > But totally misses this :( > > "" would be better returned when !CONFIG_KALLSYMS, right? I guess I'll take back my comment. I assume there are tons of embedded devices that have !CONFIG_KALLSYMS in 'release' builds, yet those devices still warn/oops sometimes; having pointers/hex numbers is really the only way to make any sense out of backtraces... yet it, basically, means that we are leaking kernel pointers. -ss