| commit | 50231352f2f376ca98f43ba975a028bcaa0d8963 | |
| author | Matthew Dillon <dillon@dragonflybsd.org> | |
| Wed, 20 Jun 2007 06:23:24 +0000 (20 06:23 +0000) | ||
| committer | Matthew Dillon <dillon@dragonflybsd.org> | |
| Wed, 20 Jun 2007 06:23:24 +0000 (20 06:23 +0000) | ||
| tree | f88ad357533a098b92a688453fb0ad206b57fd57 | treesnapshot (tar.gz zip) |
| parent | 8e990f3e488b1cc95a4fbb6e779ad298c2a2c585 | commitdiff |
Fix an issue with positive namecache timeouts. Locked children often
depend on the resolved vnode in the parent ncp's remaining intact, but
the positive namecache timeout code broke that rule and caused certain
VFS functions which depend on an intact parent (rename & remove primarily)
to occassionally return EPERM. Only zap the node if it has no children.
Reported-by: Thomas Nikolajsen <thomas.nikolajsen@mail.dk>
depend on the resolved vnode in the parent ncp's remaining intact, but
the positive namecache timeout code broke that rule and caused certain
VFS functions which depend on an intact parent (rename & remove primarily)
to occassionally return EPERM. Only zap the node if it has no children.
Reported-by: Thomas Nikolajsen <thomas.nikolajsen@mail.dk>
| sys/kern/vfs_cache.c | diffblobblamehistory |