On Thu, Nov 15, 2007 at 08:51:36AM +0100, Christian Kujau wrote: > [<c040914c>] mutex_lock_nested+0xcc/0x2c0 > [<c016dc64>] do_lookup+0xa4/0x190 > [<c016f6f9>] __link_path_walk+0x749/0xd10 > [<c016fd04>] link_path_walk+0x44/0xc0 > [<c016fd98>] path_walk+0x18/0x20 > [<c016ff98>] do_path_lookup+0x78/0x1c0 > [<c0170998>] __user_walk_fd+0x38/0x60 > [<c0169bd1>] vfs_stat_fd+0x21/0x50 > [<c0169ca1>] vfs_stat+0x11/0x20 > [<c0169cc4>] sys_stat64+0x14/0x30 > [<c01028d6>] sysenter_past_esp+0x5f/0xa5
nfsd already wedged up and holds a lock, this is expected. I'm not sure what you're doing here, but a viable work-around for now might be to use nfsv2 mounts, something like mount -o vers=2 ... or to keep v3 and disable readdirplus doing something like: mount -o vers=3,nordirplus ... The later I didn't test but was suggested on #linuxfs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
