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]
Date:   Tue, 12 Apr 2022 19:30:57 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Marco Elver <elver@...gle.com>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
        patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
        jonathanh@...dia.com, f.fainelli@...il.com,
        sudipm.mukherjee@...il.com, slade@...dewatkins.com,
        Alexander Potapenko <glider@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        kasan-dev <kasan-dev@...glegroups.com>,
        linux-mm <linux-mm@...ck.org>
Subject: Re: [PATCH 5.15 000/277] 5.15.34-rc1 review

On Tue, Apr 12, 2022 at 07:23:10PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 12, 2022 at 06:43:15PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 12, 2022 at 09:13:59PM +0530, Naresh Kamboju wrote:
> > > Hi Marco
> > > 
> > > On Tue, 12 Apr 2022 at 20:32, Marco Elver <elver@...gle.com> wrote:
> > > >
> > > > On Tue, 12 Apr 2022 at 16:16, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > > > >
> > > > > On Tue, 12 Apr 2022 at 12:11, Greg Kroah-Hartman
> > > > > <gregkh@...uxfoundation.org> wrote:
> > > > > >
> > > > > > This is the start of the stable review cycle for the 5.15.34 release.
> > > > > > There are 277 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 Thu, 14 Apr 2022 06:28:59 +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.34-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
> > > > >
> > > > >
> > > > > On linux stable-rc 5.15 x86 and i386 builds failed due to below error [1]
> > > > > with config [2].
> > > > >
> > > > > The finding is when kunit config is enabled the builds pass.
> > > > > CONFIG_KUNIT=y
> > > > >
> > > > > But with CONFIG_KUNIT not set the builds failed.
> > > > >
> > > > > x86_64-linux-gnu-ld: mm/kfence/core.o: in function `__kfence_alloc':
> > > > > core.c:(.text+0x901): undefined reference to `filter_irq_stacks'
> > > > > make[1]: *** [/builds/linux/Makefile:1183: vmlinux] Error 1
> > > > >
> > > > > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> > > > >
> > > > > I see these three commits, I will bisect and get back to you
> > > > >
> > > > > 2f222c87ceb4 kfence: limit currently covered allocations when pool nearly full
> > > > > e25487912879 kfence: move saving stack trace of allocations into
> > > > > __kfence_alloc()
> > > > > d99355395380 kfence: count unexpectedly skipped allocations
> > > >
> > > > My guess is that this commit is missing:
> > > 
> > > This patch is missing Fixes: tag.
> > > 
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f39f21b3ddc7fc0f87eb6dc75ddc81b5bbfb7672
> > > 
> > > For your information, I have reverted the below commit and build pass.
> > > 
> > > kfence: limit currently covered allocations when pool nearly full
> > > 
> > > [ Upstream commit 08f6b10630f284755087f58aa393402e15b92977 ]
> > 
> > I've added the above commit, does that fix the issue?
> > 
> > Hm, I can test that here, let me try it...
> 
> I can't duplicate the failure here with my config, let me try yours...

Yes, with your config before it fails, after I added the commit it
works.  I'll push out a -rc2 soon with that added.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ