[lkml]   [1999]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dcache problems with vfat

On Tue, 5 Jan 1999 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
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:49    [W:0.092 / U:9.660 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site