linux-kernel - [RFC] Add Debugger Test to Typical Regression Testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAO6TR8U-yrRCSQJjzWAq9nBFVyjjb8h0_73t6gQ2L1N_HRrYXg@mail.gmail.com>
Date:	Thu, 21 Jan 2016 15:07:38 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [RFC] Add Debugger Test to Typical Regression Testing

Based on recent bugs I have seen in Linux, I recommend to those
involved in regression testing of linux build tree to add a debugger
test to regression for kgdb, kdb, and mdb as a part of your standard
tests to flush out bugs in various drivers and subsystems.

The test is simple.  Load one of the debuggers on Linux, break into
the debugger console and leave the system with the processor suspended
in the debugger for 2-4 hours, then tell the debugger to "go" or "run"
and see if the system recovers.  This will flush out a lot of bugs and
recovery cases not typically seen on performance and endurance tests
and help make Linux run better on all the platforms it supports.

Many timing related or cleanup bugs will be revealed by such a test
and also allow kernel debuggers to run on a more stable platform.

This is only a suggestion.  You can download MDB or use kgdb/kdb for the test.

Jeff