Messages in this thread | | | Date | Thu, 16 Jan 2003 19:07:22 +0300 | From | Oleg Drokin <> | Subject | Re: [2.4] VFS locking problem during concurrent link/unlink |
| |
Hello!
On Thu, Jan 16, 2003 at 11:02:08AM -0500, Chris Mason wrote: > > Yes we do. > > But on the other hand I've put a check at the beginning of reiserfs_link > > and I am still seeing these links on inodes with i_nlink == 0. > That's because we don't inc the link count in reiserfs_link before we > schedule. The bug works a little like this: > link count at 1 > reiserfs_link: make new directory entry for link, schedule() > reiserfs_unlink: dec link count to zero, remove file stat data > reiserfs_link: inc link count, return thinking the stat data is still > there
That was my original yesterday's assumption. But debug prints I put in place did not confirmed it. Also if we are having a dentry pinned in memory (by sys_link), inode should not be deleted, so the statdata should stay inplace as Nikita argues.
Bye, Oleg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |