Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Naresh Kamboju]

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


>
> metadata:
>   git branch: linux-5.15.y
>   git repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
>   git commit: ff5232812521d01d1ddfd8f36559a9cf83fea928
>   git describe: v5.15.2-918-gff5232812521
>   make_kernelversion: 5.15.3-rc1
>   kernel-config: https://builds.tuxbuild.com/20yUV5tYmCSzjklEffg3Dhkbdzi/config
>
> Kernel crash log:
> -----------------
> [    1.178361] kvm [1]: Hyp mode initialized successfully
> [    1.184780] Unable to handle kernel NULL pointer dereference at
> virtual address 000000000000019b
> [    1.193599] Mem abort info:
> [    1.196394]   ESR = 0x96000044
> [    1.199458]   EC = 0x25: DABT (current EL), IL = 32 bits
> [    1.204786]   SET = 0, FnV = 0
> [    1.207848]   EA = 0, S1PTW = 0
> [    1.210998]   FSC = 0x04: level 0 translation fault
> [    1.215889] Data abort info:
> [    1.218777]   ISV = 0, ISS = 0x00000044
> [    1.222623]   CM = 0, WnR = 1
> [    1.225605] [000000000000019b] user address but active_mm is swapper
> [    1.231979] Internal error: Oops: 96000044 [#1] PREEMPT SMP
> [    1.237559] Modules linked in:
> [    1.240617] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.3-rc1 #1
> [    1.246894] Hardware name: ARM Juno development board (r2) (DT)
> [    1.252820] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [    1.259793] pc : crypto_register_alg+0x88/0xe4
> [    1.264246] lr : crypto_register_alg+0x78/0xe4
> [    1.268694] sp : ffff800012b9bce0
> [    1.272008] x29: ffff800012b9bce0 x28: 0000000000000000 x27: ffff800012644c80
> [    1.279162] x26: ffff000820d95480 x25: ffff000820d96000 x24: ffff800012644d3a
> [    1.286313] x23: ffff800012644cba x22: 0000000000000000 x21: ffff800012742518
> [    1.293463] x20: 0000000000000000 x19: ffffffffffffffef x18: ffffffffffffffff
> [    1.300614] x17: 000000000000003f x16: 0000000000000010 x15: ffff000800844a1c
> [    1.307765] x14: 0000000000000001 x13: 293635326168732c x12: 2973656128636263
> [    1.314916] x11: 0000000000000010 x10: 0101010101010101 x9 : ffff80001054b5a8
> [    1.322066] x8 : 7f7f7f7f7f7f7f7f x7 : fefefefefeff6462 x6 : 0000808080808080
> [    1.329217] x5 : 0000000000000000 x4 : 8080808080800000 x3 : 0000000000000000
> [    1.336367] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff800012742518
> [    1.343517] Call trace:
> [    1.345962]  crypto_register_alg+0x88/0xe4
> [    1.350062]  crypto_register_skcipher+0x80/0x9c
> [    1.354600]  simd_skcipher_create_compat+0x19c/0x1d0
> [    1.359572]  cpu_feature_match_AES_init+0x9c/0xdc
> [    1.364284]  do_one_initcall+0x50/0x2b0
> [    1.368125]  kernel_init_freeable+0x250/0x2d8
> [    1.372488]  kernel_init+0x30/0x140
> [    1.375981]  ret_from_fork+0x10/0x20
> [    1.379562] Code: 2a0003f6 710002df aa1503e0 1a9fd7e1 (3906b261)
> [    1.385667] ---[ end trace a032e96fc9ec202d ]---
> [    1.390350] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b
> [    1.398018] SMP: stopping secondary CPUs
> [    1.401947] Kernel Offset: disabled
> [    1.405434] CPU features: 0x10001871,00000846
> [    1.409794] Memory Limit: none
> [    1.412849] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x0000000b ]---
>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> build link:
> -----------
> https://builds.tuxbuild.com/20yUV5tYmCSzjklEffg3Dhkbdzi/build.log
>
> build config:
> -------------
> https://builds.tuxbuild.com/20yUV5tYmCSzjklEffg3Dhkbdzi/config

- Naresh

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Greg Kroah-Hartman]

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

Is this also an issue on 5.16-rc1?

thanks,

greg k-h

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Jon Hunter]

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


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.

Jon

-- 
nvpublic

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Naresh Kamboju]

On Tue, 16 Nov 2021 at 14:18, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> 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
>
> Is this also an issue on 5.16-rc1?

Not an issue on 5.16-rc1.
5.16-rc1 boot successful on arm64 juno-r2 / qemu-arm64.

- Naresh

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Geert Uytterhoeven]

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")

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Greg Kroah-Hartman]

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

Re: [PATCH 5.15 000/917] 5.15.3-rc1 review

[Greg Kroah-Hartman]

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@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...

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

greg k-h