linux-kernel - [PATCH 0/4] [GIT PULL] ktest: Updates for 3.18

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>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 07 Oct 2014 17:16:31 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/4] [GIT PULL] ktest: Updates for 3.18


Linus,

A fix and a clean up to ktest, as well as two small features.

 A way to allow users to skip a manual bisect.
 Allowing cherry picked patches to be tested.

The cherry pick worked for a test I needed, but stressing it may
not have all the desired effects. It doesn't cause any regressions
so I kept it in.

Please pull the latest ktest-v3.18 tree, which can be found at:


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

Tag SHA1: 48c20121c5971c194410fa229d5797811a25a9e8
Head SHA1: d832d743385dd5e735660951aa9d7d36a6a4176a


Chris J Arges (1):
      ktest: add ability to skip during BISECT_MANUAL

Steven Rostedt (Red Hat) (3):
      ktest: Add PATCHCHECK_CHERRY
      ktest: Fix check for new kernel success on rebooting to good kernel
      ktest: Don't bother with bisect good or bad on replay

----
 tools/testing/ktest/ktest.pl    | 61 +++++++++++++++++++++++++++++++----------
 tools/testing/ktest/sample.conf | 10 +++++++
 2 files changed, 57 insertions(+), 14 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/