On Tue, Oct 17, 2017 at 04:46:22PM -0500, Ryan Arnold wrote:
Some projects with a more disciplined testing approach ask developers to submit reasonably complete feature based tests along side the enablement patch and in the future a new test is required for each encountered regression. If at least the latter is enforced it can build reasonable coverage over time.
Is it premature to work with the test suite projects right now to make sure that these regressions (dhclient & KASAN) have a test created _somewhere_ to document them?
Well, it's always possible to contribute tests to relevant testsuites. You might have trouble finding a sensible existing testsuite for some things, and there will be plenty of issues where finding a sensible test is also unreasonably difficult so you're not going to have much chance of making it a requirement in the forseeable future.
KASAN is just an option that needs turning on in builds, it's not something you'd write a test for. It is already covered in kernelci, looks like it and a bunch of the other test configurations have been blacklisted for the stable kernels though so someone ought to look at reenabling it - there were a bunch of build fixes that were backported a while ago, probably fixes to enable KASAN were part of it or it was just blacklisted at a point where no stable kernels worked.