i already reported this little nuisance starting in 2.0.21 to linux-smp a
month ago, and see it happen in all the subsequent kernel releases up to
the current 2.0.24:
- compiling nfs as a module _without_ SMP support works as expected.
- compiling nfs as a module _WITH_ SMP support activated yields "unresolved
symbols" in nfs.o
- insmod .../nfs.o dies with pointing to the unresolved symbols:
active_kernel_processor
kernel_counter
kernel_flag
smp_invalidate_needed
smp_spins
- According to .depend in the fs/nfs subdirectory _only_ inode.c has smp
relevant include directives:
#include <linux/smp.h>
#include <linux/smp_lock.h>
Hope this info helps the experts to track down this little nuisance with
nfs module support and SMP.
I can perfectly live with compiling nfs support into the kernel, but as
this major kernel 2.0 is pretty close to become a stable one, newbies
(including myself) might become irritated !
Thanks and PLEASE NOTE, that I'm not subscribed to linux-kernel !!!
So please answer to linux-smp or private email.
Michael
--
===========================================================
The opinions expressed above are solely those of the author
and are not necessarily those of Schering.
===========================================================
NAME: Dr. Michael Grimm ADDRESS: Schering AG
EMAIL: michael.grimm@schering.de IPCH/TCH
PHONE: +49-30-468-5477 D-13342 Berlin
FAX: +49-30-4691-6741 Germany
===========================================================