On Thu, Aug 10, 2023 at 09:14:43AM -0700, Guenter Roeck wrote: > On Wed, Aug 09, 2023 at 12:39:47PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 6.1.45 release. > > There are 127 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 Fri, 11 Aug 2023 10:36:10 +0000. > > Anything received after that time might be too late. > > > > Build results: > total: 157 pass: 153 fail: 4 > Failed builds: > loongarch:defconfig > loongarch:allnoconfig > loongarch:tinyconfig > loongarch:allmodconfig > Qemu test results: > total: 521 pass: 513 fail: 8 > Failed tests: > arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:rootfs > arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:rootfs > <all loongarch> > > loongarch failures as already reported, introduced with v6.1.44. > > The failed arm tests crash in f2fs (again - previously reported > against the v6.1.43 release candidate). > > [ 6.685458] 8<--- cut here --- > [ 6.685593] Unable to handle kernel NULL pointer dereference at virtual address 00000034 > [ 6.685725] [00000034] *pgd=00000000 > [ 6.686010] Internal error: Oops: 5 [#1] SMP ARM > [ 6.686209] CPU: 0 PID: 194 Comm: seedrng Not tainted 6.1.45-rc1-00128-g02a4c6c322d1 #1 > [ 6.686350] Hardware name: Generic DT based system > [ 6.686467] PC is at f2fs_issue_flush+0x160/0x210 > [ 6.686821] LR is at f2fs_do_sync_file+0x7c8/0xaa8 Odd that you are the only one seeing this f2fs report, does no one else use f2fs on 6.1 systems? thanks, greg k-h
