On Sat, 10 Jul 2004, Thomas Moestl wrote: > > Never the less I'm sure there is a race in waitq.c of autofs4 in > > 2.4 that seems to cause this problem. This is one of the things > > addressed by my patch. > > The system in question still uses autofs3. While I believe that the > waitq race is also present there (it could probably cause directory > lookups to hang, if I understand it correctly), I do not think that > any autofs3 code could cause exactly those symptoms that I have > observed. For that, it would have to obtain dentries of the file > systems that it has mounted, but the old code never does that.
I don't think autofs v3 has this race. It uses the BKL everywhere to serialise execution. Never the less people seem to see the "busy inode" messages sometimes. Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
