Whoever did the dentry changes to knfsd broke this. The way it used to
work was that lookup would never follow symlinks; by definition of the
spec, it should always return the symlink inode itself. It is then
up to the client to call READLINK and interpret the resulting pathname
(and there are a multitude of ways to deal with that, BTW).
The problem is that currently, vfs.c:nfsd_lookup calls dentry_lookup
with a follow_link argument of 1. That should be 0.
Olaf
-- Olaf Kirch | --- o --- Nous sommes du soleil we love when we play okir@monad.swb.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax okir@caldera.de +-------------------- Why Not?! -----------------------