On Mon, Apr 18, 2005 at 12:58:50PM +0400, Artem B. Bityuckiy wrote: > On Mon, 2005-04-18 at 09:51 +0100, Christoph Hellwig wrote: > > No, exporting locks is a really bad idea. Please try to find a better > > method to fix your problem that doesn't export random kernel symbols. > > > In general it must be true. But this specific case I believe is > reasonable enough to export the mutext (as an exception).
Umm, no. It's absolutely not a good reason. What jffs2 is doing right now is to poke into VFS internals it shouldn't, and exporting more internals to prevent it from doing so isn't making the situation any better. The VFS already has a method for freeing an struct inode pointer, and that is ->destroy_inode. You're probably better off updating your GC state from that place. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
