On Fri, Oct 25, 2013 at 1:50 PM, Rusty Russell <ru...@rustcorp.com.au> wrote: > Ming Lei <tom.leim...@gmail.com> writes: >> On Fri, Oct 25, 2013 at 7:08 AM, Rusty Russell <ru...@rustcorp.com.au> wrote: >>> >>> Sorry, I was imprecise. I was referring to the kernel's kallsyms >>> tables produced by scripts/kallsyms.c. This patch left them in the >>> the kallsyms tables and filtered them out from /proc/kallsyms. >> >> Yes, but it isn't easy to do it by script/kallsyms.c , and IMO, it should >> be correct to hide them for user space but keep them in kallsyms table. > > So they'll appear in backtraces? And turn up randomly for other symbol > dereferences? > > I don't think you really want this!
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. Thanks, -- Ming Lei -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
