linux-kernel - Re: [PATCH 5.15 000/917] 5.15.3-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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YZO60LxGc6Ii1Ixl@kroah.com>
Date:   Tue, 16 Nov 2021 15:06:08 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Jon Hunter <jonathanh@...dia.com>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Shuah Khan <shuah@...nel.org>,
        Florian Fainelli <f.fainelli@...il.com>, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, stable <stable@...r.kernel.org>,
        Pavel Machek <pavel@...x.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Anders Roxell <anders.roxell@...aro.org>,
        Vladis Dronov <vdronov@...hat.com>,
        Arnd Bergmann <arnd@...db.de>,
        "David S. Miller" <davem@...emloft.net>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

On Tue, Nov 16, 2021 at 11:39:52AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 16, 2021 at 11:12:23AM +0100, Geert Uytterhoeven wrote:
> > Hi Jon,
> > 
> > On Tue, Nov 16, 2021 at 10:23 AM Jon Hunter <jonathanh@...dia.com> wrote:
> > > On 16/11/2021 08:48, Greg Kroah-Hartman wrote:
> > > > On Tue, Nov 16, 2021 at 02:09:44PM +0530, Naresh Kamboju wrote:
> > > >> On Tue, 16 Nov 2021 at 12:06, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > > >>>
> > > >>> On Tue, 16 Nov 2021 at 00:03, Greg Kroah-Hartman
> > > >>> <gregkh@...uxfoundation.org> wrote:
> > > >>>>
> > > >>>> This is the start of the stable review cycle for the 5.15.3 release.
> > > >>>> There are 917 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, 17 Nov 2021 16:52:23 +0000.
> > > >>>> 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.15.3-rc1.gz
> > > >>>> or in the git tree and branch at:
> > > >>>>          git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > > >>>> and the diffstat can be found below.
> > > >>>>
> > > >>>> thanks,
> > > >>>>
> > > >>>> greg k-h
> > > >>>
> > > >>>
> > > >>
> > > >> Regression found on arm64 juno-r2 / qemu.
> > > >> Following kernel crash reported on stable-rc 5.15.
> > > >>
> > > >> Anders bisected this kernel crash and found the first bad commit,
> > > >>
> > > >> Herbert Xu <herbert@...dor.apana.org.au>
> > > >>     crypto: api - Fix built-in testing dependency failures
> > 
> > That's commit adad556efcdd ("crypto: api - Fix built-in testing
> > dependency failures")
> > 
> > > I am seeing the same for Tegra as well and bisect is pointing to the
> > > above for me too.
> > > > Is this also an issue on 5.16-rc1?
> > >
> > > I have not observed the same issue for 5.16-rc1.
> > 
> > Following the "Fixes: adad556efcdd" chain:
> > 
> > cad439fc040efe5f ("crypto: api - Do not create test larvals if manager
> > is disabled")
> > beaaaa37c664e9af ("crypto: api - Fix boot-up crash when crypto manager
> > is disabled")
> 
> Argh, yes, I didn't run my "check for fixes for patches in the queue"
> script which would have caught these.  I'll go queue these up and a few
> others that it just caught...

Now fixed up, along with another "fix for the fix for the fix" patch
that was needed.

greg k-h