Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752784AbaA3JXJ (ORCPT ); Thu, 30 Jan 2014 04:23:09 -0500 Received: from mail-ea0-f182.google.com ([209.85.215.182]:39153 "EHLO mail-ea0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751122AbaA3JXG (ORCPT ); Thu, 30 Jan 2014 04:23:06 -0500 Date: Thu, 30 Jan 2014 10:23:02 +0100 From: Ingo Molnar To: Mathias Krause Cc: Linus Torvalds , "H. Peter Anvin" , Richard Weinberger , "H. Peter Anvin" , Kees Cook , Cong Ding , Ingo Molnar , Linux Kernel Mailing List , Michael Davidson , Thomas Gleixner , Wei Yongjun Subject: Re: [GIT PULL] x86/kaslr for v3.14 Message-ID: <20140130092301.GB2862@gmail.com> References: <52E7D2E5.8090208@linux.intel.com> <52E7D9FF.1080506@nod.at> <52E7DB15.3090808@zytor.com> <20140128170507.GA16279@gmail.com> <20140128194823.GA18702@gmail.com> <20140129081128.GA31489@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Mathias Krause wrote: > On 29 January 2014 09:11, Ingo Molnar wrote: > >> But you can see that the symbol is perfectly fine: > >> > >> (gdb) list *(schedule+0x45) > > > > Oh, cool. Thanks for that trick - this will save me quite some time in > > the future. > > > > So we can strip absolute addresses just fine from oopses - cool. > > > > I'd even argue to strip the hex on non-randomized kernels as long as > > there's kallsyms around, and only print hex if we don't have any > > symbols. > > Please, don't do so! I do find the hex values in the backtrace > *very* useful as I'm using 'objdump -wdr vmlinux | less' quite often > to "browse around" in the kernel binary. Grepping for addresses from > a backtrace works quite nicely this way. Having to lookup symbols > and do base-16 arithmetics in the head (or a shell, for that matter) > would only slow down this process. So, please leave the hex values > in place. They do help a lot -- at least in the non-kASLR case. Well, if the consensus is that they help then we better make them correct in the KASLR case as well ... Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/