> > Obviously my patch isn't the real solution, the real solution is to > > make the new function calls use a consistent 64-bit type, or figure > > out what in my code path is calling these functions and check it for > > value sanity.
I would be tempted to do both computations and print then inputs as well as do a WARN_ON when they differ. That will give you a stack trace of the offender, and providing you return the "correct" value you can see how it continues functioning afterwards. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
