linux-kernel - Re: [PATCH 4.9 00/50] 4.9.170-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]

Date:   Sat, 20 Apr 2019 09:04:14 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Sasha Levin <sashal@...nel.org>
Cc:     Guenter Roeck <linux@...ck-us.net>, 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.9 00/50] 4.9.170-stable review

On Fri, Apr 19, 2019 at 09:12:45PM -0400, Sasha Levin wrote:
> On Fri, Apr 19, 2019 at 01:16:37PM -0700, Guenter Roeck wrote:
> > On Fri, Apr 19, 2019 at 12:39:26PM -0700, Guenter Roeck wrote:
> > > On Thu, Apr 18, 2019 at 07:57:11PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.9.170 release.
> > > > There are 50 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 Sat Apr 20 16:03:22 UTC 2019.
> > > > Anything received after that time might be too late.
> > > >
> > > Build results:
> > > 	total: 172 pass: 170 fail: 2
> > > Failed builds:
> > > 	i386:tools/perf
> > > 	x86_64:tools/perf
> > 
> > Caused by "tools include: Adopt linux/bits.h". That isn't really
> > a bug fix, and since it is the last commit in the perf directory
> > it isn't needed either. Reverting it fixes the problem.
> 
> Indeed. I'll remove it from all branches since it doesn't look like a
> fix to begin with.

My fault with that one, sorry about that.

greg k-h