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: <1294243887.26623.26.camel@gandalf.stny.rr.com>
Date:	Wed, 05 Jan 2011 11:11:27 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <greg@...ah.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Tim Bird <tim.bird@...sony.com>, lmr <lmr@...hat.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Vivek Goyal <vgoyal@...hat.com>, Jon Masters <jcm@...hat.com>
Subject: [GIT PULL] Add ktest.pl to tools/testing/ktest

Linus (et. al.)

As I announced at Kernel Summit, I created a simple kernel test program
that allows a developer to test their kernels with various randconfigs.

It also performs automated git bisects, and serial patch testing.

It can even do a config bisect, which I've used several times to find
that one config that breaks the kernel.

Each of these tests have three kinds of test types:

1) build - This is the simplest of the tests. It just makes sure that
the kernel compiles without error.

2) boot - This not only builds the kernel, but also makes sure that the
kernel boots. You need to have a way to read the console via stdout,
which the tool checks to see if you make it to a login prompt (or
something else if you change the config file).

3) test - This builds, and boots the kernel, and on success of booting,
it will execute some command. You could do a 'ssh host ...' to remotely
kick off a test. It can be any shell script that must exit with 0 on
success and non zero on error.

It comes with a very documented sample config file and a test (for me)
that makes sure all the options in ktest.pl exist also in the sample
config file, so I do not forget to document any new features.

Most of the configs have defaults that you do not need to worry about. I
could add lots of small sample configs for people to start with too.

Anyway, a lot of people asked me to push this into the kernel, so I'm
posting my pull request now. I've kept the history of the development in
the git tree. I'm not posting all the patches as I'm not sure people
care about them. Below is the diffstat and change log. For the final
result of ktest.pl your can see these files:

http://rostedt.homelinux.com/ktest/ktest.pl
http://rostedt.homelinux.com/ktest/sample.conf
http://rostedt.homelinux.com/ktest/compare-ktest-sample.pl

The previous announcement can be found here:

http://marc.info/?l=linux-kernel&m=128925992719659&w=2

The following patches are in:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-ktest.git

    branch: master


Steven Rostedt (30):
      Initial start of ktest.pl
      ktest: New features: noclean, dodie, poweroff on error and success
      ktest: New features reboot on error, make options
      ktest: Bisecting, install modules, add logging
      ktest: Added better console, add test build
      ktest: Added reboot on success
      ktest: Added patchcheck
      ktest: Add reverse bisect, better logging, copyright
      ktest: Added continuing on success, clear log and timeout
      ktest: Add open and close console and start stop monitor
      ktest: Added sample.conf, new %default option format
      ktest: Add POST_INSTALL to allow initrds to be created
      ktest: Add poweroff after halt and powercycle after reboot
      ktest: New TEST_START instead of using [], and use real SHA1s
      ktest: Update the sample config file with more documentation
      ktest: Use oldnoconfig instead of yes command
      ktest: Write to stdout if no log file is given
      ktest: Use $output_config instead of typing $outputdir/.config
      ktest: Allow a test case to undefine a default value
      ktest: Output something easy to parse for failure or success
      ktest/cleanups: Added version 0.2, ssh as options
      ktest: Added config_bisect test type
      ktest: Added compare script to test ktest.pl to sample.conf
      ktest: Updated the sample.conf for the latest options
      ktest: Use different temp config name for minconfig
      ktest: Parse off the directory name in useconfig for failures
      ktest: Added force stop after success and failure
      ktest: For grub reboot, use run_ssh instead of run_command
      ktest: Copy the last good and bad configs in config_bisect
      ktest: Ask for the manditory config options instead of just failing

----
 tools/testing/ktest/compare-ktest-sample.pl |   30 +
 tools/testing/ktest/ktest.pl                | 2023 +++++++++++++++++++++++++++
 tools/testing/ktest/sample.conf             |  622 ++++++++
 3 files changed, 2675 insertions(+), 0 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ