On Fri, May 21, 2004 at 05:58:26PM +0100, James Pearson wrote: > Not quite sure what you mean by this - I had tried Greg's patch > (http://marc.theaimsgroup.com/?l=linux-nfs&m=107604754127538&w=2) > previously - but it made no difference in my case. The kernel I'm using > now has both Greg's patch and Ian's recent autofs4 patch.
The error message and subsequent oops are both generic symptoms and could come from any kind of race with umount which causes a dentry or inode reference count leak, not just the particular one in NFS which I fixed. There could well be another NFS bug like this, or one in autofs. Ian's patch may have fixed it, hidden it, or just stopped tickling it. The only way to tell for sure is to modify the code that generates the message to BUG() instead and use a kernel debugger to figure out what has gone wrong. Note that using a debugger at oops time is already too late. James, are you able to reproduce this at will? Greg. -- Greg Banks, R&D Software Engineer, SGI Australian Software Group. I don't speak for SGI. _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
