linux-kernel - Re: [ANNOUNCE] ktest.pl: Easy and flexible testing script for Linux Kernel Developers

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

Date:	Thu, 28 Oct 2010 23:56:59 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Greg KH <gregkh@...e.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Jon Masters <jcm@...hat.com>, corbet <corbet@....net>,
	Jake Edge <jake@....net>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	lmr@...hat.com, autotest@...t.kernel.org,
	Vivek Goyal <vgoyal@...hat.com>,
	Clark Williams <williams@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: [ANNOUNCE] ktest.pl: Easy and flexible testing script for
 Linux Kernel Developers

On Thu, 2010-10-28 at 20:41 -0700, Greg KH wrote:
> > 
> > Should I try to get this into 2.6.37?  Since it is a stand alone tool, I
> > can hardly expect that it would break anything else.
> 
> I don't see why not, but perhaps you might want to wait for people to
> test it a bit?  Then get it into .38?

That's sorta the catch-22. We want testers before pushing it into
mainline, but if it is in mainline we get more testers :-)

I'm not sure it makes a difference now if it goes in or if it does not.
Because it would reside in tools as a helper program, and will not
affect the quality of the kernel whether it's in the kernel tree or not.
Although, I could argue that it may help the quality of the kernel if it
is in the kernel tree because it may have more people testing the
kernel.

One thing I worry about adding it to the tools directory. I could
imagine someone running the tool from the tools directly from the build
source that they are testing. If they do a bisect, a bisect may remove
the tools directory while its running. That would be an interesting
test ;-)

-- Steve

--
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/