On Sat, Jul 13, 2019 at 06:16:56AM -0700, Guenter Roeck wrote:
On 7/13/19 1:22 AM, Greg Kroah-Hartman wrote:
On Fri, Jul 12, 2019 at 01:21:41PM -0700, Guenter Roeck wrote:
On Fri, Jul 12, 2019 at 05:30:35PM +0200, Greg Kroah-Hartman wrote:
On Fri, Jul 12, 2019 at 02:26:57PM +0100, Jon Hunter wrote:
Hi Greg,
On 12/07/2019 13:17, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.1.18 release. There are 138 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 14 Jul 2019 12:14:36 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.18-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.1.y and the diffstat can be found below.
thanks,
greg k-h
Pseudo-Shortlog of commits:
Both are now dropped, thanks. I'll push out a -rc2 with that changed.
Can you push that update into the git repository ? v5.1.17-137-gde182b90f76d still has the problem.
Odd, I thought I did this. Pushed out again just to be sure.
Problem is still seen in -rc2.
Ugh, I dropped one, but not the other, now both gone. I'll push out updates in a bit.
Also:
Building powerpc:ppc6xx_defconfig ... failed
drivers/crypto/talitos.c: In function ‘get_request_hdr’: include/linux/kernel.h:979:51: error: dereferencing pointer to incomplete type ‘struct talitos_edesc’
Seen with both v4.19.58-92-gd66f8e7 and v5.1.17-137-gde182b90f76d.
This problem is caused by "crypto: talitos - fix hash on SEC1.", which will need a proper backport - struct talitos_edesc is declared later in the source file.
Ick, let me go drop this one after breakfast...
Turns out this affects all three branches (v4.19. v5.1, and v5.2).
Ok, dropping it now (sorry, longer than just breakfast...)
greg k-h