[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874n82gk89.fsf@rustcorp.com.au>
Date: Mon, 28 Oct 2013 13:44:30 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Ming Lei <tom.leiming@...il.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Chen Gang <gang.chen@...anux.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol
Ming Lei <tom.leiming@...il.com> writes:
> On Fri, Oct 25, 2013 at 7:58 PM, Rusty Russell <rusty@...tcorp.com.au> 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?
I don't know... It would be your job, as the person making the change,
to find all the users of kallsyms and prove that.
This is why it is easier not to include incorrect values in the kernel's
kallsyms in the first place.
Hope that helps,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists