From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
stable <stable@vger.kernel.org>, Pavel Machek <pavel@denx.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Anders Roxell <anders.roxell@linaro.org>,
Vladis Dronov <vdronov@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
"David S. Miller" <davem@davemloft.net>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.15 000/917] 5.15.3-rc1 review
Date: Tue, 16 Nov 2021 11:39:52 +0100 [thread overview]
Message-ID: <YZOKeFT8NGenpbsU@kroah.com> (raw)
In-Reply-To: <CAMuHMdXG2Y-rwPtBw1PsGckk3MLRQvn6Xht6ts2RkW7Zkx=w2w@mail.gmail.com>
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@nvidia.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@linaro.org> wrote:
> > >>>
> > >>> On Tue, 16 Nov 2021 at 00:03, Greg Kroah-Hartman
> > >>> <gregkh@linuxfoundation.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@gondor.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...
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-16 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211115165428.722074685@linuxfoundation.org>
[not found] ` <CA+G9fYtFOnKQ4=3-4rUTfVM-fPno1KyTga1ZAFA2OoqNvcnAUg@mail.gmail.com>
[not found] ` <CA+G9fYuF1F-9TAwgR9ik_qjFqQvp324FJwFJbYForA_iRexZjg@mail.gmail.com>
[not found] ` <YZNwcylQcKVlZDlO@kroah.com>
2021-11-16 9:20 ` [PATCH 5.15 000/917] 5.15.3-rc1 review Jon Hunter
2021-11-16 10:12 ` Geert Uytterhoeven
2021-11-16 10:39 ` Greg Kroah-Hartman [this message]
2021-11-16 14:06 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YZOKeFT8NGenpbsU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdronov@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox