linux-kernel - Re: [PATCH 3.18 000/178] 3.18.15-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:	Thu, 11 Jun 2015 10:52:00 -0700
From:	Kevin Hilman <khilman@...nel.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
	stable-commits@...r.kernel.org,
	Tyler Baker <tyler.baker@...aro.org>,
	Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 3.18 000/178] 3.18.15-review

Sasha Levin <sasha.levin@...cle.com> writes:

> On 06/09/2015 01:17 PM, Kevin Hilman wrote:
>> Hi Sasha,
>> 
>> On Mon, Jun 8, 2015 at 6:39 AM, Sasha Levin <sasha.levin@...cle.com> wrote:
>>> This is the start of the stable review cycle for the 3.18.15 release.
>>> There are 178 patches in this series, all will be posted as a response
>>> to this one.  If anyone has any issues with these being applied, please
>>> let me know.
>> 
>> We've started build/boot testing your 3.18 stable queue with the
>> automated build/boot tools at the kernelci.org project.  We'll soon be
>> sending automated reports to this list for your stable queue (and
>> other stable trees.)  Until we have the email reports automated, below
>> is the report for this review series which has a whole pile of build
>> failures across x86, arm and arm64.
>> 
>> Kevin
>
> Thanks for the report(s)!
>
> I've fixed the issues and re-pushed.
>

Build looks good now.  I only have one remaining build failure[1] for
ARM multi_v7_defconfig with CONFIG_THUMB2_KERNEL=y enabled[1].  I had
already posted a fix for that patch to stable, but it's missing in your
queue so I replied to that patch to help you find it.

It also looks good for boot testing at kernelci.org[2].  The boot failures
here aren't specific to your queue, but are NFSroot issues for these
boards with v3.18 in general.

Thanks,

Kevin

[1] http://kernelci.org/build/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/?fail

[2]
stable-sasha boot: 206 boots: 4 failed, 202 passed (v3.18.14-167-g25798d3d2163)

Full Boot Summary:
http://kernelci.org/boot/all/job/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/
Full Build Summary:
http://kernelci.org/build/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/

Tree: stable-sasha
Branch: local/linux-3.18.y-queue
Git Describe: v3.18.14-167-g25798d3d2163
Git Commit: 25798d3d216334361a51ac37429a83c1faa5e97d
Git URL:
git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
Tested: 67 unique boards, 19 SoC families, 26 builds out of 143

Boot Failures Detected:
http://kernelci.org/boot/?v3.18.14-167-g25798d3d2163&fail

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