Re: Modular filesystem using drop_inode would need inode_lock

From: Christoph Hellwig
Date: Fri Jul 09 2004 - 16:53:22 EST


On Fri, Jul 09, 2004 at 02:43:32PM -0700, Luck, Tony wrote:
> This is mostly a logical inconsistency at the moment (since the
> only filesystem that has a "drop_inode" function defined in its
> super_operations is hugetlbfs, and it is unlikely to move out of
> the kernel and into a module). But the ->drop_inode() function
> is called with inode_lock held, and it is expected to drop the
> lock ... which would be impossible for a module as the lock is
> not exported.

->drop_inode is a bad idea anyway. Please send a pointer to your
filesystem so we can fix it.

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