That's what I do now.
> Keep in mind that if you are sharing an interrupt vector, each
> and every interrupt handler gets called for each and every
> interrupt, so having the device driver check that the device to
> which it is attached is really generating an interrupt is
> simple good form.
This is already being done. But I do REALLY paranoid checking of
each and every parameter of every function that is not declared 'static'.
But in this case the caller of the function or the hardware is
doing really strange things and it should be fixed ASAP and this
is the best way to catch the caller ;-)
-- Science is what we can tell a computer. Art is everything else. --- D.E.Knuth - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/