linux-kernel - Re: Build regressions/improvements in v4.3-rc7

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: <20151025220701.GA5635@debian>
Date:	Sun, 25 Oct 2015 23:07:01 +0100
From:	Rabin Vincent <rabin@....in>
To:	Afzal Mohammed <afzal.mohd.ma@...il.com>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Kees Cook <keescook@...omium.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc7

On Mon, Oct 26, 2015 at 12:33:18AM +0530, Afzal Mohammed wrote:
> On Sun, Oct 25, 2015 at 06:38:18PM +0100, Geert Uytterhoeven wrote:
> > I think we should have at least one arm-nommu platform in the upstream kernel,
> > with a suitable defconfig, so 0build will catch regressions.
> 
> afaik, there are 4 arm-nommu defconfig's. Has been recently playing
> with Vybrid nommu platform, did not notice any build error w/ it's
> defconfig (vf610m4) and able to boot too. Just now tried -rc7, it too
> was success.

vf610m4 won't use patch.c since it has CONFIG_XIP_KERNEL=y.  The failing
config is a randconfig[1], but the error can be triggered by, for
example, enabling CONFIG_JUMP_LABEL=y on lpc18xx_defconfig.

[1] http://kisskb.ellerman.id.au/kisskb/buildresult/12531538/
--
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/