David Holland <dholland-t...@netbsd.org> wrote: > When calling lookup, the parent (directory) is supposed to be locked > to prevent exactly this sort of thing from happening. You and/or > perfuse and/or puffs ignore this at your peril, because doing so > violates atomicitiy guarantees and assumptions made by upper-level > code.
I don't violate the need for a locked vnode during lookup, the problem is with distributed filesystem, where another machine delete the directory. > However, if it's really disappeared, why not just fail with ENOENT? ENOENT tells the kernel that the entry it looked up does not exists. It does not tell anything about the parent vnode being now stale. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org
