green b67f04e53c Fix an upper-vnode leak created in revision 1.52. When an upper-layer ...

file has been removed, it should be purged from the cache, but it need
not be removed from the directory stack causing corruption; instead,
it will simply be removed once the last references and holds on it
are dropped at the end of the unlink/rmdir system calls, and the
normal !UN_CACHED VOP_INACTIVE() handler for unionfs finishes it off.

This is easily reproduced by repeated "echo >file; rm file" on a
unionfs mount.  Strangely, "echo -n >file; rm file" didn't make
it happen.

2004-01-16 16:31:01 +00:00

..

union_subr.c

Fix an upper-vnode leak created in revision 1.52. When an upper-layer

2004-01-16 16:31:01 +00:00

union_vfsops.c

Remove now unused variable.

2003-11-01 15:04:50 +00:00

union_vnops.c

Fix an upper-vnode leak created in revision 1.52. When an upper-layer

2004-01-16 16:31:01 +00:00

union.h

Factor out the process of freeing ``directory caches'', which unionfs

2003-06-14 23:27:29 +00:00