linux-kernel - Re: [PATCH 3.4 00/65] 3.4.110-rc1 review

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]

Message-ID: <5627475A.2090203@huawei.com>
Date:	Wed, 21 Oct 2015 16:05:46 +0800
From:	Zefan Li <lizefan@...wei.com>
To:	Guenter Roeck <linux@...ck-us.net>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
CC:	<lizf@...nel.org>, stable <stable@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 3.4 00/65] 3.4.110-rc1 review

>>>>> Build results:
>>>>>           total: 97 pass: 96 fail: 1
>>>>> Failed builds:
>>>>>           m68k:sun3_defconfig
>>>>>
>>>>> Qemu test results:
>>>>>           total: 63 pass: 63 fail: 0
>>>>>
>>>>> Build failure is due to inconsistent kallsyms data when building
>>>>> m68k:sun3_defconfig.
>>>>>   From the build log:
>>>>>
>>>>> Inconsistent kallsyms data
>>>>> This is a bug - please report about it
>>>>> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
>>>>> Makefile:922: recipe for target 'vmlinux' failed
>>>>>
>>>>> Bisect says that the problem is caused by "vfs: Test for and handle paths
>>>>> that are unreachable from  their mnt_root", and reverting that patch
>>>>>   fixes the problem. No idea what is going on. Copying Eric and Geert.
>>>
>>> This is odd...
>>
>> sun3_defconfig builds fine for me with gcc-4.1.2 20061115 (prerelease)
>> (Ubuntu 4.1.1-21) and with gcc-4.9.0 (kernel.org crosstool).
>>
> Passes for me as well with 4.9.0 from kernel.org crosstool.
>

Thanks for testing!

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