Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752249Ab3JZMbO (ORCPT ); Sat, 26 Oct 2013 08:31:14 -0400 Received: from mail-vb0-f54.google.com ([209.85.212.54]:56155 "EHLO mail-vb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751306Ab3JZMbN (ORCPT ); Sat, 26 Oct 2013 08:31:13 -0400 MIME-Version: 1.0 In-Reply-To: <87sivp7eai.fsf@rustcorp.com.au> References: <1382498320-26594-1-git-send-email-tom.leiming@gmail.com> <87eh7bfoq9.fsf@rustcorp.com.au> <20131024084559.GD16735@n2100.arm.linux.org.uk> <87mwlyclng.fsf@rustcorp.com.au> <87y55h7vcd.fsf@rustcorp.com.au> <87sivp7eai.fsf@rustcorp.com.au> Date: Sat, 26 Oct 2013 20:31:12 +0800 Message-ID: Subject: Re: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol From: Ming Lei To: Rusty Russell Cc: Russell King - ARM Linux , Andrew Morton , Linux Kernel Mailing List , Chen Gang , linux-arm-kernel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 24 On Fri, Oct 25, 2013 at 7:58 PM, Rusty Russell wrote: >> >> Basically these symbols are only used to generate code, and in >> kernel mode, CPU won't run into the corresponding addresses >> because the generate code is copied to other address during booting, >> so I understand they won't appear in backtraces. > > An oops occurs when something went *wrong*. We look up all kinds of > stuff. Are you so sure that *none* of the callers will ever see these > strange symbols and produce a confusing result? Suppose that might happen, kernel should be smart enough to know that the address is not inside kernel address space and won't produce confusing result, right? Thanks, -- Ming Lei -- 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/