linux-kernel - Re: [PATCH 4.16 00/55] 4.16.10-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]

Message-ID: <20180518135630.GG24822@kroah.com>
Date:   Fri, 18 May 2018 15:56:30 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.16 00/55] 4.16.10-stable review

On Fri, May 18, 2018 at 06:29:57AM -0700, Guenter Roeck wrote:
> On 05/18/2018 01:14 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.10 release.
> > There are 55 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.
> > 
> > Responses should be made by Sun May 20 08:14:42 UTC 2018.
> > Anything received after that time might be too late.
> > 
> 
> For v4.16.9-56-gde63ee0:
> 
> Build results:
> 	total: 143 pass: 142 fail: 1
> Failed builds:
> 	xtensa:allmodconfig
> Qemu test results:
> 	total: 139 pass: 139 fail: 0
> 
> Build failure:
> 
> include/linux/mlx5/driver.h: In function ‘mlx5_get_vector_affinity_hint’:
> include/linux/mlx5/driver.h:1284:13: error: ‘struct irq_desc’ has no member named ‘affinity_hint’
> 
> The build failure is inherited from mainline with 'net/mlx5: Fix
> mlx5_get_vector_affinity function' and affects all non-SMP builds with that
> driver enabled. Still not fixed in mainline.
> 
> Details are available at http://kerneltests.org/builders/.

Wonderful, thanks for testing all 3 of these and letting me know.

Hopefully someday that upstream breakage will get fixed...

greg k-h