Hi Rob.... On Sat, Dec 11, 2010 at 00:23, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: > On Fri, 10 Dec 2010, Mulyadi Santosa wrote: >> >> then i did cat /proc/kallsyms | grep rday_3 >> >> i can see the rday_3 in that file,But still I am unable to insmod the m3.ko >> >> The address you gave....if I apply 3:1 VM split just like x86..means >> it's out of kernel address space. So, could you confirm what VM split >> your current kernel use? > > but how could that cause a problem? surely that would cause > problems with *all* module loading, not just my simple example. It's just my couriousity.... who knows somehow the symbol is mistakenly relocated outside kernel address space? >> what if we use EXPORT_SYMBOL_GPL()? And what I am afraid is that all >> those symbol are wiped out due to optimization. > > i considered that for a second but if the symbol was wiped out, why > is it still showing up in the /proc/kallsyms file? because EXPORT_SYMBOL doesn't care whether it's eventually exported or not? just my suspicion.. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
