linux-kernel - Re: [PATCH 3.16 00/17] 3.16.1-stable 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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 09 Aug 2014 08:04:17 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, satoru.takeuchi@...il.com,
	shuah.kh@...sung.com, stable@...r.kernel.org
Subject: Re: [PATCH 3.16 00/17] 3.16.1-stable review

On 08/09/2014 07:16 AM, Greg Kroah-Hartman wrote:
[ .. ]
>> Just for reference, in mainline, we currently have
>> 	total: 133 pass: 127 fail: 6
>> plus four (!) qemu tests failing (arm, mips, mips64, and ppc),
>> meaning there will be three more dropped configurations (all arm
>> as far as I can see), and there is already a bunch of failures.
>> This is with v3.16-9794-g8065be8. next-20140808 build result is
>> 	total: 133 pass: 121 fail: 12
>> with the same failed qemu tests, so it will only get worse :-(.
>>
>> Some improved quality assurance may be helpful going forward,
>> especially since many of the failures seem to be due to lack of
>> (build) testing and could easily have been avoided. Something
>> to discuss in Chicago, maybe.
>
> I wonder if it is just due to the merge not being finished yet?  The
> 0-day built-bot should have caught any major build issues before now
> with the individual trees, so there shouldn't be any reason you should
> be seeing failures :(
>

There are two arm build failures in Linus' tree which are not seen
in -next. Those are either merge problems, or maybe there is some
other series of arm patches coming. Either case, the arm folks are
pretty good at tracking failures, so I assume those will be fixed
soon (especially since multi_v7_defconfig is one of the failing
builds). The other build failures are all seen in -next as well,
so they _should_ be known.

For the qemu failures, they are all the same in -next and in the
tip of Linus' tree, so I guess no one tested the configurations
I use for qemu tests. I only recently added -next to the list of
branches to test, so I only noticed the failures after they showed up
in Linus' tree.

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/