Nick Piggin <npiggin@xxxxxxx> writes: >> hch mentioned that it would be good to instrument to what file system >> the inode belonged. Anything else you'd like to look at? > > Not too sure. I guess i_state. Maybe you could take s_umount lock > and see if it is still mounted? > > Actually most useful will be to find all places where i_mapping is > set to NULL, and record in the inode some callchain for the last > site which set i_mapping to NULL. Dump this stack when you hit the > bug. Well, I can't find a single place where i_mapping is set to NULL. ;-) I'll see what I can dig up. Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
