linux-kernel - Re: Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1

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]

Message-ID: <20150709165944.GA19282@twins.programming.kicks-ass.net>
Date:	Thu, 9 Jul 2015 18:59:44 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Mark Langsdorf <mlangsdo@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1

On Thu, Jul 09, 2015 at 11:46:04AM -0500, Mark Langsdorf wrote:
> I did a git bisect and it looks like the faulty patch is
> d72da4a4d973d8a0a0d3c97e7cdebf287fbe3a99, "rbtree: Make lockless
> searches non-fatal". I can't see why it causes my builds to fail,
> but if I revert that patch and the related series, then I can
> build the kernel and build tools/perf successfully.
> 
> Any insight into a less intensive way of fixing my build would
> be appreciated.

This is tools/perf failing to build right? Add tip/perf/urgent, it
appears to contain the required bits to make it go again.

The /urgent branches will get to Linus 'soon' I imagine.
--
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/