linux-kernel - Re: [PATCH 4.4 000/312] 4.4.223-rc1 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] [day] [month] [year] [list]

Message-ID: <20200508142613.GA426400@kroah.com>
Date:   Fri, 8 May 2020 16:26:13 +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.4 000/312] 4.4.223-rc1 review

On Fri, May 08, 2020 at 06:54:11AM -0700, Guenter Roeck wrote:
> On 5/8/20 6:44 AM, Greg Kroah-Hartman wrote:
> > On Fri, May 08, 2020 at 06:37:56AM -0700, Guenter Roeck wrote:
> >> On 5/8/20 5:29 AM, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 4.4.223 release.
> >>> There are 312 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, 10 May 2020 12:29:44 +0000.
> >>> Anything received after that time might be too late.
> >>>
> >>
> >> This is not a complete list of errors.
> > 
> > Yeah, I knew this was going to be a rough one.  I was hoping the "early
> > warning" messages from Linaro would have caught most of these, oh well
> > :(
> > 
> 
> To be fair, I had noticed the errors yesterday. I just thought this was
> so bad that it looked like a stray (bad) push to me, and I didn't send
> feedback. Maybe I should always send feedback if I see errors prior to
> an -rc release. I don't want to spam people with noise, so I am not sure.
> Any thoughts on that ?

If the tree is broken, I'd like to know about it.  Rarely do I know that
it is broken and leave it alone.  One exception would be last night when
it was too late for me to fix the build issues, but Sasha was kind
enough to do so.

So it's not noise to me, if it's easy enough for you to do so.

I think I fixed up the MIPS stuff, turns out gcc was just crashing on a
filesystem driver with an internal error.  I think I need a different
version of gcc if I want to build more arches...

I'll go push out a -rc with this fixed up now, thanks.

greg k-h