linux-kernel - Re: [PATCH v2] early_printk: consolidate random copies of identical code

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

Date:	Thu, 7 Mar 2013 20:10:43 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Mike Frysinger <vapier@...too.org>,
	Ingo Molnar <mingo@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Russell King <linux@....linux.org.uk>,
	Michal Simek <monstr@...str.eu>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mundt <lethal@...ux-sh.org>,
	"David S. Miller" <davem@...emloft.net>,
	Chris Metcalf <cmetcalf@...era.com>,
	Richard Weinberger <richard@....at>
Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical
 code

On Thu, Mar 07, 2013 at 07:49:35PM -0500, Paul Gortmaker wrote:
> 
> Within an hour, Fengguang's robots[1] found the branch, were compiling
> it for fringe architectures, and running sparse on it, and sending me the
> sparse regressions.  I'd listened to Fengguang's presentation while at
> KS in San Diego, but I had no idea it was this proactive, until it did
> autobot testing on my branch.

And people wonder why I wanted to give Fengguang a round of applauds
there. I guess I was one of the first people to get his testing, as it
found a lot of little things for me that my own tests missed.

> 
> I have most of the prebuilt toolchains[2], and two line wrappers to set
> the ARCH/CROSS_COMPILE, but as it stands, it seems I really don't
> need those any more.  I can sanity test on a common arch and then
> simply push to kernel.org to trigger build sanity across all arch.  I'll
> probably still continue to use the toolchain prebuilts to test locally
> though, just for the peace of mind.  But knowing FW bots are doing
> testing before it goes into linux-next or anywhere else is really nice.
> 

I should stress that there's a sample ktest.pl file for everyone:

 tools/testing/ktest/examples/crosstests.conf

Just download the cross compilers from:

 (assuming you're running on an x86_64 box)

  https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/

Install them somewhere like:

  /usr/local

ie.

  /usr/local/gcc-4.6.3-nolibc/mips-linux/bin/mips-linux-gcc

Have a pristine checkout, and a build directory to use:

 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux.git
 mkdir cross-compile

Then just run:

  ktest.pl crosstests.conf

It will go arch by arch cross compiling each with the defconfig. Feel
free to modify that config. But really, there should be no more excuses
for kernel developers not doing cross compiles of most archs. It's
really that simple.

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