linux-kernel - Re: [PATCH 4.16 00/72] 4.16.9-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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180514165147.GB30141@kroah.com>
Date:   Mon, 14 May 2018 18:51:47 +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/72] 4.16.9-stable review

On Mon, May 14, 2018 at 09:27:58AM -0700, Guenter Roeck wrote:
> On Mon, May 14, 2018 at 08:48:17AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.9 release.
> > There are 72 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 Wed May 16 06:47:58 UTC 2018.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
> 	total: 143 pass: 142 fail: 1
> Failed builds: 
> 	m68k:allmodconfig
> Qemu test results:
> 	total: 139 pass: 139 fail: 0
> 
> Building m68k:allmodconfig ... failed:
> 
> ERROR: "__udivdi3" [drivers/mtd/nand/nand.ko] undefined!
> ERROR: "__divdi3" [drivers/mtd/nand/nand.ko] undefined!
> 
> The problem is caused by upstream commit 3057fcef3853 ("mtd: rawnand: Make
> sure we wait tWB before polling the STATUS reg"). This is one of the "bug
> for bug compatible with upstream" situations, meaning the upstream build
> is broken as well.

I've dropped the offending patch for now, and pushed out a -rc2.

Thanks for testing all of these and letting me know.

greg k-h