Re: dcache problems with vfat

Alexander Viro (viro@math.psu.edu)
Tue, 5 Jan 1999 16:53:51 -0500 (EST)


On Tue, 5 Jan 1999 Andries.Brouwer@cwi.nl wrote:

> > Maybe vfat does something that confuses the child lists?
>
> If I am not mistaken (hope to find time later this evening
> to look a little bit more into this) it is simply this:
>
> A dcache entry referring to some inode is created: i_count=1.
> A second dcache entry referring to the same inode is created
> because revalidate() on the first one failed. Now i_count=2.
> For rmdir the test for an empty directory vfat_empty() fails:
> if (dir->i_count > 1)
> return -EBUSY;
>
> Off-hand I tend to agree with your first reply, that the first
> dcache entry should not just be dropped but released entirely,
> so that i_count is decreased again.

The first entry was dropped, right, but it still remains our cwd.
So cd .. should get rid of it. Looks like it didn't.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/