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:	Mon, 18 Jul 2016 21:00:39 +0800
From:	Fengguang Wu <lkp@...el.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	Thierry Reding <thierry.reding@...il.com>,
	linux-kernel@...r.kernel.org,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: running "make dtbs" for test builds

On Mon, Jul 18, 2016 at 02:52:32PM +0200, Arnd Bergmann wrote:
>On Monday, July 18, 2016 8:41:22 PM CEST Fengguang Wu wrote:
>> Hi Arnd,
>>
>> On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote:
>> >Hi Fengguang,
>> >
>> >I've recently run into a number of cases in which I pulled a branch that
>> >was building fine with "make vmlinux", but that failed for "make dtbs",
>> >and I wonder if this is something that could be checked by the kbuild
>> >test robot so we catch it earlier.
>>
>> We initially run "make" without vmlinux, however during bisect more
>> specific make targets will be used to speed it up. To do that it's
>> necessary to know the regex patterns of "make dtbs" error messages,
>> so that they can be correctly bisected.
>>
>> Can you give some "make dtbs" error messages or patterns?
>>
>
>A typical error looks like
>
>Error: arch/arm/boot/dts/sun7i-a20-bananapi-m1-plus.dts:252.1-18 Label or path usb_power_supply not found
>FATAL ERROR: Syntax error parsing input tree
>scripts/Makefile.lib:312: recipe for target 'arch/arm/boot/dts/sun7i-a20-bananapi-m1-plus.dtb' failed
>make[3]: *** [arch/arm/boot/dts/sun7i-a20-bananapi-m1-plus.dtb] Error 1
>
>There should be almost 100% correlation between seeing "arch/${ARCH}/boot/dts/"
>in stderr and having a problem in the "make dtbs" stage.

Got it, thank you for the tips!

Regards,
Fengguang

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ