Re: [PATCH 6.1 000/194] 6.1.47-rc1 review

[Greg Kroah-Hartman]

On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
> On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
> > > On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.47 release.
> > > > There are 194 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, 23 Aug 2023 19:40:45 +0000.
> > > > Anything received after that time might be too late.
> > > >
> > >
> > > Build results:
> > >       total: 157 pass: 156 fail: 1
> > > Failed builds:
> > >       m68k:sun3_defconfig
> > > Qemu test results:
> > >       total: 521 pass: 519 fail: 2
> > > Failed tests:
> > >       arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs
> > >       arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
> > >
> > > The m68k build failure is
> > >
> > > Inconsistent kallsyms data
> > > Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> > >
> > > I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help.
> > > Nothing to worry about. The f2fs crashes are still seen. They
> > > also happen for other architectures, so it is not just an arm problem.
> > > I'll probably just disable all f2fs testing going forward. If so I'll
> > > send a note clarifying that the lack of reported test failures doesn't
> > > mean that it works.
> >
> > I'll look into this later this week, next week to resolve the f2fs
> > stuff.  I wanted to get to the other known bug fixes first.
> >
> > > For x86 I get the same runtime warning as everyone else.
> >
> > Yeah, this is troubling...
> >
> > Is it clang only?  I'll dig into this today...
> 
> It is seen with gcc-13 and clang-17 with few extra configs.
> We are not booting defconfig.
> 
> The Kconfigs are enabled with KFENCE.
> 
> I see this from lore
> "
> This is from overnight testing that hit this only in the KCSAN runs.
> The KASAN and non-debug runs had no trouble.
> 
> Thanx, Paul
> 
> "

Ok, that's good, it's not going to hit "normal" users...  :)

> 
> steps to reproduce:
> -------------------
> tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-13
> --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5XRO5x4/config
> 
> 
> Here is the links to details and build details,
> [1]
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.46-195-g5165f4e9738c/testrun/19256276/suite/log-parser-boot/test/check-kernel-exception/details/
> 
> [2]
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5XRO5x4/
> 
> [3]
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5XRO5x4/config

You are going to force me to use tuxmake again, aren't you...

I'll dig into this after lunch.

greg k-h