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  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:	Fri, 08 Aug 2014 03:45:09 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Davidlohr Bueso <davidlohr@...com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Aswin Chandramouleeswaran <aswin@...com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] arch,locking: Ciao arch_mutex_cpu_relax()

On 08/07/2014 06:18 PM, Davidlohr Bueso wrote:
> On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
>> On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
>>> It looks like you forgot to update frv?  It's been failing on -next since a
>>> few days:
>
> Anyway developers can be alerted sooner about this (ie: while its still
> in -next phase), like automated emails or something? This would be extra
> nice for those archs that are harder to get tested.
>
Not sure if that would help. After all, images are being built.
People just don't care enough to have a look.

FWIW, next-20140808 build results on my build/test farm:
	total: 132 pass: 120 fail: 12
Failed builds:
	frv:defconfig
	mips:nlm_xlp_defconfig
	openrisc:defconfig
	powerpc:allmodconfig (binutils 2.23 and 2.24)
	powerpc:mpc83xx_defconfig (ditto)
	powerpc:mpc85xx_defconfig (ditto)
	powerpc:mpc85xx_smp_defconfig (ditto)
	unicore32:defconfig

with qemu test runs failing for arm, mips, mips64, and ppc.

Which points to the next problem: I simply do not have the time to track down
all those failures, and I would guess neither do others who might be interested.
Geert is doing an excellent job trying to report and fix things, but quite frankly
sometimes one feels like Sisyphus trying to keep builds clean.

Guenter

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