Re: 2.4.5-ac12 -- Unresolved symbols in drivers/net/wan/comx.o -- "proc_get_inode"

Keith Owens (kaos@ocs.com.au)
Sun, 10 Jun 2001 17:30:27 +1000


On Sun, 10 Jun 2001 03:12:06 -0400 (EDT),
Frank Davis <fdavis112@juno.com> wrote:
> It appears that fs/proc/inode.o (where proc_get_inode() is defined)
>is not being included when comx.o is built . Keith, I'm not too familar
>the build's dependencies process to know if drivers/net/wan/Makefile
>should be modified or another build file.

One long line of 255 characters reformatted for readability. Also your
mailer appended Miles's original text without any attribution and
without quoting it, making it look as though you (Frank Davis) wrote
the bug report. You need a better mailer for linux-kernel. Having
got that off my chest (and added attribution and quoting) ...

>Miles T Lane wrote
>>find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i
>>-r ln -sf ../{} pcmcia
>>if [ -r System.map ]; then /sbin/depmod -ae -F
>>System.map 2.4.5-ac12; fi
>>depmod: *** Unresolved symbols in
>>/lib/modules/2.4.5-ac12/kernel/drivers/net/wan/comx.o
>>depmod: proc_get_inode

fs/proc/inode.c is included, it is a fundamental part of /proc. The
problem is that proc_get_inode is not listed as an exported symbol.
Interesting that nobody else has reported this, proc_get_inode has
never been exported in the 2.4 series and comx.c has not changed in
this area either, looks like nobody else has tried to run comx as a
module.

The obvious fix is to add EXPORT_SYMBOL(proc_get_inode) to
fs/proc/root.c but I am not sure that the obvious fix is the correct
one. All the other uses of proc_get_inode are in the proc system,
should another subsystem be delving into proc internals? I'm going to
bounce this one to the proc and comx maintainers to let them decide
amongst themselves. Hmmm, no official proc maintainer so it's off to
l-k for this mail.

-
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/