> I looked also at other 1394 drivers and all have the calls in 'bad' order. > Sure this ordering has to be reversed or it is correct and is triggering > other hidden bug ? > Quite possibly it's triggering (or is triggered by) some other bug. There is also a possibility that raw1394.c might be doing something wrong and gets away with it with the changed ordering. Because dv1394.c does it the "seemingly-bad" way and I haven't got rmmod to hang while removing it.
Can anyone answer this - in what cases will generic_delete_inode hang on __down_failed -> default_wake_function -> __down? Thanks Parag - 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/
