> Timings and race conditions are difficult to test. Another problem is
> that we'll hardly will be able to cover all the possible cases. If
> you try to check for things like for example the handling of hardware
> errors (r/w errors on disks, ...) you'll have to add special code to
> "inject" errors.
This is a possibility - you can do some wonderfully wicked things with
modules. We could write a generic script to generate and compile a module
to exercise a given internal kernel function if we decide we need that
level of testing.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."