Today's Linux next 20221122 tag clang-15 tinyconfig builds fails on
powerpc and s390 architectures.
Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM_IAS=0 ARCH=s390
CROSS_COMPILE=s390x-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache
clang'
kernel/printk/printk.c:95:1: error: type specifier missing, defaults
to 'int'; ISO C99 and later do not support implicit int
[-Werror,-Wimplicit-int]
DEFINE_STATIC_SRCU(console_srcu);
^
int
kernel/printk/printk.c:95:20: error: a parameter list without types is
only allowed in a function definition
DEFINE_STATIC_SRCU(console_srcu);
^
kernel/printk/printk.c:261:29: error: use of undeclared identifier
'console_srcu'
srcu_read_lock_held(&console_srcu));
^
kernel/printk/printk.c:288:33: error: use of undeclared identifier
'console_srcu'
return srcu_read_lock_nmisafe(&console_srcu);
^
kernel/printk/printk.c:300:28: error: use of undeclared identifier
'console_srcu'
srcu_read_unlock_nmisafe(&console_srcu, cookie);
^
kernel/printk/printk.c:3122:20: error: use of undeclared identifier
'console_srcu'
synchronize_srcu(&console_srcu);
^
kernel/printk/printk.c:3469:20: error: use of undeclared identifier
'console_srcu'
synchronize_srcu(&console_srcu);
^
kernel/printk/printk.c:3521:20: error: use of undeclared identifier
'console_srcu'
synchronize_srcu(&console_srcu);
^
8 errors generated.
log:
https://builds.tuxbuild.com/2HtTqOb2b83eGTzpS4bjLf59Agd/
Build history:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221122/te…
--
Linaro LKFT
https://lkft.linaro.org
LKFT detected arm64 boot regression on today's Linux next-20221121 tag.
The Kernel boot log did not show anything on the serial console.
Anders bisected this problem and found the subject commit is the
first bad commit.
# first bad commit: [9ed2b4616d4e846ece2a04cb5007ce1d1bd9e3f3]
arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
Later it was found this lore link which was already reported [1].
ref:
[1] https://lore.kernel.org/all/Y3pS5fdZ3MdLZ00t@dev-arch.thelio-3990X/
--
Linaro LKFT
https://lkft.linaro.org
On Mon, 21 Nov 2022 at 08:28, Naresh Kamboju <naresh.kamboju(a)linaro.org> wrote:
>
> Hi Dave,
>
> On Fri, 18 Nov 2022 at 05:24, Dave Hansen <dave.hansen(a)intel.com> wrote:
> >
> > On 11/17/22 15:23, Marco Elver wrote:
> > > Yes - it's the 'level != PG_LEVEL_4K'.
> >
> > That plus the bisect made it pretty easy to find, thanks for the effort!
> >
> > Could you double-check that the attached patch fixes it? It seemed to
> > for me.
>
> I have applied the attached patch on Linux next 20221118 and tested [1].
> The reported issue has been fixed now.
>
> Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
> Tested-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
> Tested-by: Naresh Kamboju <naresh.kamboju(a)linaro.org>
>
> OTOH,
> I request you to walk through the boot and test log [1] (new see few failures).
> not ok 7 - test_double_free
> not ok 9 - test_invalid_addr_free
> not ok 11 - test_corruption
> not ok 18 - test_kmalloc_aligned_oob_write
> # kfence: pass:19 fail:4 skip:2 total:25
> # Totals: pass:19 fail:4 skip:2 total:25
> not ok 6 - kfence
Fixed by https://lkml.kernel.org/r/20221118152216.3914899-1-elver@google.com
