powerpc: io-defs.h:43:1: error: performing pointer arithmetic on a null pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
The Powerpc clang builds failed due to following warnings / errors on the Linux next-20240416 tag. Powerpc: - tqm8xx_defconfig + clang-17 - Failed - allnoconfig + clang-17 - Failed - tinyconfig + clang-17 - Failed Reported-by: Linux Kernel Functional Testing Build log: In file included from arch/powerpc/kernel/ptrace/ptrace.c:19: In file included from include/linux/syscalls.h:93: In file included from include/trace/syscall.h:7: In file included from include/linux/trace_events.h:9: In file included from include/linux/hardirq.h:11: In file included from arch/powerpc/include/asm/hardirq.h:6: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/powerpc/include/asm/io.h:672: arch/powerpc/include/asm/io-defs.h:43:1: error: performing pointer arithmetic on a null pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic] 43 | DEF_PCI_AC_NORET(insb, (unsigned long p, void *b, unsigned long c), | ^~~ 44 | (p, b, c), pio, p) | ~~ Links: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240416/testrun/23495171/suite/build/test/clang-17-tqm8xx_defconfig/details/ - https://storage.tuxsuite.com/public/linaro/lkft/builds/2fAvI3mKJ0dTHcazPrLl2zNF9JO/ -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH] bug: Fix no-return-statement warning with !CONFIG_BUG
On Wed, 10 Apr 2024 at 21:02, Adrian Hunter wrote:
>
> BUG() does not return, and arch implementations of BUG() use unreachable()
> or other non-returning code. However with !CONFIG_BUG, the default
> implementation is often used instead, and that does not do that. x86 always
> uses its own implementation, but powerpc with !CONFIG_BUG gives a build
> error:
>
> kernel/time/timekeeping.c: In function ‘timekeeping_debug_get_ns’:
> kernel/time/timekeeping.c:286:1: error: no return statement in function
> returning non-void [-Werror=return-type]
>
> Add unreachable() to default !CONFIG_BUG BUG() implementation.
>
> Fixes: e8e9d21a5df6 ("timekeeping: Refactor timekeeping helpers")
> Reported-by: Naresh Kamboju
> Closes:
> https://lore.kernel.org/all/CA+G9fYvjdZCW=7zgxs6a_3bysjq56yf7s-+pnlq_8a4dkh1...@mail.gmail.com/
> Signed-off-by: Adrian Hunter
This patch applied on top of today's Linux next-20240410 tag and
build test pass.
Tested-by: Linux Kernel Functional Testing
> ---
> include/asm-generic/bug.h | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
--
Linaro LKFT
https://lkft.linaro.org
Re: [PATCH 00/14] Add support for suppressing warning backtraces
On Tue, 12 Mar 2024 at 22:33, Guenter Roeck wrote: > This series is based on the RFC patch and subsequent discussion at > https://patchwork.kernel.org/project/linux-kselftest/patch/02546e59-1afe-4b08-ba81-d94f3b691c9a@moroto.mountain/ > and offers a more comprehensive solution of the problem discussed there. Thanks for the patchset. This patch series applied on top of Linux next and tested. Tested-by: Linux Kernel Functional Testing -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH] powerpc: include linux/backlight.h from asm/backlight.h
Hi Jani and Benjamin,
On Mon, 4 Mar 2024 at 15:31, Jani Nikula wrote:
>
> On Mon, 04 Mar 2024, Jani Nikula wrote:
> > Removal of the backlight include from fb.h uncovered an implicit
> > dependency in powerpc asm/backlight.h. Add the explicit include.
> >
> > Reported-by: Naresh Kamboju
> > Closes:
> > https://lore.kernel.org/r/ca+g9fysak5tbqqxfc2w4ohlga0cbthmxbeq8qayfxtu75yi...@mail.gmail.com
> > Fixes: 11b4eedfc87d ("fbdev: Do not include in header")
> > Cc: Thomas Zimmermann
> > Cc: Helge Deller
> > Cc: linux-fb...@vger.kernel.org
> > Signed-off-by: Jani Nikula
> >
> > ---
> >
> > Not even compile tested!
>
> Naresh, please try this patch!
Thanks for the proposed fix patch.
Steps to reproduce:
# tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13
--kconfig ppc6xx_defconfig --kconfig-add CONFIG_PMAC_BACKLIGHT=y
config debugkernel dtbs kernel modules xipkernel
# Applying patch set
Applying: fbdev/chipsfb: Include
The reported build regression is fixed but build failed with below errors.
My two cents,
I should have copied the full build error log in the morning.
Few more build errors on powerpc builds,
--
drivers/macintosh/via-pmu-backlight.c: In function
'__pmu_backlight_update_status':
drivers/macintosh/via-pmu-backlight.c:74:21: error: implicit
declaration of function 'backlight_get_brightness'; did you mean
'pmu_backlight_get_level_brightness'?
[-Werror=implicit-function-declaration]
74 | int level = backlight_get_brightness(bd);
| ^~~~
| pmu_backlight_get_level_brightness
drivers/macintosh/via-pmu-backlight.c: At top level:
drivers/macintosh/via-pmu-backlight.c:108:21: error: variable
'pmu_backlight_data' has initializer but incomplete type
108 | static const struct backlight_ops pmu_backlight_data = {
| ^
drivers/macintosh/via-pmu-backlight.c:109:10: error: 'const struct
backlight_ops' has no member named 'update_status'
109 | .update_status = pmu_backlight_update_status,
| ^
drivers/macintosh/via-pmu-backlight.c:109:27: warning: excess elements
in struct initializer
109 | .update_status = pmu_backlight_update_status,
| ^~~
drivers/macintosh/via-pmu-backlight.c:109:27: note: (near
initialization for 'pmu_backlight_data')
drivers/macintosh/via-pmu-backlight.c: In function 'pmu_backlight_init':
drivers/macintosh/via-pmu-backlight.c:136:37: error: storage size of
'props' isn't known
136 | struct backlight_properties props;
| ^
drivers/macintosh/via-pmu-backlight.c:154:34: error: invalid
application of 'sizeof' to incomplete type 'struct
backlight_properties'
154 | memset(, 0, sizeof(struct backlight_properties));
| ^~
drivers/macintosh/via-pmu-backlight.c:155:22: error:
'BACKLIGHT_PLATFORM' undeclared (first use in this function)
155 | props.type = BACKLIGHT_PLATFORM;
| ^~
drivers/macintosh/via-pmu-backlight.c:155:22: note: each undeclared
identifier is reported only once for each function it appears in
drivers/macintosh/via-pmu-backlight.c:157:14: error: implicit
declaration of function 'backlight_device_register'; did you mean
'root_device_register'? [-Werror=implicit-function-declaration]
157 | bd = backlight_device_register(name, NULL, NULL,
_backlight_data,
| ^
| root_device_register
drivers/macintosh/via-pmu-backlight.c:166:19: error: invalid use of
undefined type 'struct backlight_device'
166 | level = bd->props.max_brightness;
| ^~
drivers/macintosh/via-pmu-backlight.c:176:35: error: invalid use of
undefined type 'struct backlight_device'
176 | bd->props.max_brightness / 15);
| ^~
drivers/macintosh/via-pmu-backlight.c:179:11: error: invalid use of
undefined type 'struct backlight_device'
179 | bd->props.brightness = level;
| ^~
drivers/macintosh/via-pmu-backlight.c:180:11: error: invalid use of
undefined type 'struct backlight_device'
180 | bd->props.power = FB_BLANK_UNBLANK;
| ^~
drivers/macintosh/via-pmu-backlight.c:181:9: error: implicit
declaration of function 'backlight_update_status'; did you mean
'pmu_backlight_update_status'? [-Werror=implicit-function-declaration]
181 | backlight_update_status(bd);
| ^~~
| pmu_backlight_update_status
drivers/macintosh/via-pmu-backlight.c:136:37: warning: unused variable
'props' [-Wunused-variable]
136 |
Powerpc: ps3av.c:(.text+0x19e8): undefined reference to `video_get_options'
I encountered the following build warnings/errors while compiling the powerpc kernel on Linux next-20240208 .. next-20240212 tag with clang toolchain. Reported-by: Linux Kernel Functional Testing powerpc64le-linux-gnu-ld: drivers/ps3/ps3av.o: in function `ps3av_probe': ps3av.c:(.text+0x19e8): undefined reference to `video_get_options' make[3]: *** [/builds/linux/scripts/Makefile.vmlinux:37: vmlinux] Error 1 make[3]: Target '__default' not remade because of errors. Links: - https://storage.tuxsuite.com/public/linaro/lkft/builds/2cFkli5H02fikrpga6PluAWLAMa/ -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.15 00/67] 5.15.142-rc1 review
On Tue, 5 Dec 2023 at 09:10, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.15.142 release. > There are 67 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, 07 Dec 2023 03:14:57 +. > 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.142-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 Following powerpc build failures noticed. * powerpc, build - clang-17-defconfig - FAILED - gcc-12-defconfig - FAILED - gcc-8-defconfig - FAILED build error: --- arch/powerpc/platforms/pseries/iommu.c: In function 'find_existing_ddw': arch/powerpc/platforms/pseries/iommu.c:908:49: error: 'struct dma_win' has no member named 'direct' 908 | *direct_mapping = window->direct; | ^~ suspected commit: powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device [ Upstream commit 3bf983e4e93ce8e6d69e9d63f52a66ec0856672e ] Reported-by: Linux Kernel Functional Testing Links: - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.141-68-gbff845be423f/testrun/21492943/suite/build/test/gcc-12-defconfig/details/ - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.141-68-gbff845be423f/testrun/21492943/suite/build/test/gcc-12-defconfig/history/ -- Linaro LKFT https://lkft.linaro.org
Powerpc: maple_defconfig: kernel/rtas_pci.c:46:5: error: no previous prototype for function 'rtas_read_config' [-Werror,-Wmissing-prototypes]
Following Powerpc maple_defconfig and other builds failed with gcc-13 / 8 and clang toolchains on Linux next-20231127 tag. build: * gcc-8-cell_defconfig * gcc-8-maple_defconfig * gcc-8-tinyconfig * gcc-13-tinyconfig * gcc-13-cell_defconfig * gcc-13-maple_defconfig * clang-17-cell_defconfig * clang-17-tinyconfig * clang-17-maple_defconfig * clang-nightly-cell_defconfig * clang-nightly-maple_defconfig * clang-nightly-tinyconfig Reported-by: Linux Kernel Functional Testing Build logs: --- arch/powerpc/kernel/rtas_pci.c:46:5: error: no previous prototype for function 'rtas_read_config' [-Werror,-Wmissing-prototypes] 46 | int rtas_read_config(struct pci_dn *pdn, int where, int size, u32 *val) | ^ arch/powerpc/kernel/rtas_pci.c:46:1: note: declare 'static' if the function is not intended to be used outside of this translation unit 46 | int rtas_read_config(struct pci_dn *pdn, int where, int size, u32 *val) | ^ | static arch/powerpc/kernel/rtas_pci.c:98:5: error: no previous prototype for function 'rtas_write_config' [-Werror,-Wmissing-prototypes] 98 | int rtas_write_config(struct pci_dn *pdn, int where, int size, u32 val) | ^ arch/powerpc/kernel/rtas_pci.c:98:1: note: declare 'static' if the function is not intended to be used outside of this translation unit 98 | int rtas_write_config(struct pci_dn *pdn, int where, int size, u32 val) | ^ | static 2 errors generated. make[5]: *** [scripts/Makefile.build:243: arch/powerpc/kernel/rtas_pci.o] Error 1 steps to reproduce: # tuxmake --runtime podman --target-arch powerpc --toolchain clang-17 --kconfig maple_defconfig LLVM=1 LLVM_IAS=0 LD=powerpc64le-linux-gnu-ld Links: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20231127/testrun/21324129/suite/build/test/clang-17-maple_defconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20231127/testrun/21324129/suite/build/test/clang-17-maple_defconfig/history/ - https://storage.tuxsuite.com/public/linaro/lkft/builds/2Yk9XaK95NuGJL9barjaXrOWxib/ -- Linaro LKFT https://lkft.linaro.org
next: arch/powerpc/kernel/stacktrace.c:171:9: error: implicit declaration of function 'nmi_cpu_backtrace'
Following build regressions noticed on Linux next-20230619. Reported-by: Linux Kernel Functional Testing Regressions found on powerpc: - build/clang-nightly-maple_defconfig - build/gcc-8-maple_defconfig - build/gcc-12-maple_defconfig - build/clang-nightly-cell_defconfig - build/gcc-12-cell_defconfig - build/gcc-8-cell_defconfig - build/clang-16-cell_defconfig - build/clang-16-maple_defconfig Build log: arch/powerpc/kernel/stacktrace.c: In function 'handle_backtrace_ipi': arch/powerpc/kernel/stacktrace.c:171:9: error: implicit declaration of function 'nmi_cpu_backtrace' [-Werror=implicit-function-declaration] 171 | nmi_cpu_backtrace(regs); | ^ arch/powerpc/kernel/stacktrace.c: In function 'arch_trigger_cpumask_backtrace': arch/powerpc/kernel/stacktrace.c:226:9: error: implicit declaration of function 'nmi_trigger_cpumask_backtrace'; did you mean 'arch_trigger_cpumask_backtrace'? [-Werror=implicit-function-declaration] 226 | nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); | ^ | arch_trigger_cpumask_backtrace cc1: all warnings being treated as errors Links: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230619/testrun/17629288/suite/build/test/gcc-12-cell_defconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230619/testrun/17629288/suite/build/test/gcc-12-cell_defconfig/history/ - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230619/testrun/17629288/suite/build/test/gcc-12-cell_defconfig/details/ Steps to reproduce: # To install tuxmake to your home directory at ~/.local/bin: # pip3 install -U --user tuxmake # # Or install a deb/rpm depending on the running distribution # See https://tuxmake.org/install-deb/ or # https://tuxmake.org/install-rpm/ # # See https://docs.tuxmake.org/ for complete documentation. tuxmake --runtime podman --target-arch powerpc --toolchain gcc-12 --kconfig cell_defconfig -- Linaro LKFT https://lkft.linaro.org
next: gcc-8-ppc6xx_defconfig: ERROR: modpost: "__divdi3" [sound/pci/emu10k1/snd-emu10k1.ko] undefined!
Linux next powerpc gcc-8 build failed on Linux next 20230516 and 20230517. - build/gcc-8-ppc6xx_defconfig Reported-by: Linux Kernel Functional Testing Build log: make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build \ ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- \ 'CC=sccache powerpc64le-linux-gnu-gcc' \ 'HOSTCC=sccache gcc' ERROR: modpost: "__divdi3" [sound/pci/emu10k1/snd-emu10k1.ko] undefined! ERROR: modpost: "__udivdi3" [sound/pci/emu10k1/snd-emu10k1.ko] undefined! make[2]: *** [/builds/linux/scripts/Makefile.modpost:136: Module.symvers] Error 1 make[2]: Target '__modpost' not remade because of errors. make[1]: *** [/builds/linux/Makefile:1978: modpost] Error 2 links, - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230517/testrun/17031706/suite/build/test/gcc-8-ppc6xx_defconfig/log - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230517/testrun/17031706/suite/build/test/gcc-8-ppc6xx_defconfig/history/ Steps to reproduce: === # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. # Original tuxmake command with fragments listed below. tuxmake --runtime podman --target-arch powerpc --toolchain gcc-8 --kconfig ppc6xx_defconfig -- Linaro LKFT https://lkft.linaro.org
next: powerpc: gpio_mdio.c:(.text+0x13c): undefined reference to `__of_mdiobus_register'
Following build failures noticed on Linux next-20230419 for powerpc. Regressions found on powerpc: - build/gcc-8-defconfig - build/clang-16-defconfig - build/gcc-12-defconfig - build/clang-nightly-defconfig Reported-by: Linux Kernel Functional Testing Build log: powerpc64le-linux-gnu-ld: arch/powerpc/platforms/pasemi/gpio_mdio.o: in function `gpio_mdio_probe': gpio_mdio.c:(.text+0x13c): undefined reference to `__of_mdiobus_register' powerpc64le-linux-gnu-ld: drivers/net/phy/phy_device.o: in function `phy_probe': phy_device.c:(.text+0x56ac): undefined reference to `devm_led_classdev_register_ext' powerpc64le-linux-gnu-ld: drivers/net/ethernet/pasemi/pasemi_mac.o: in function `pasemi_mac_open': pasemi_mac.c:(.text+0x19ac): undefined reference to `of_phy_connect' make[2]: *** [scripts/Makefile.vmlinux:35: vmlinux] Error 1 Build details: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230419/testrun/16369015/suite/build/test/gcc-12-defconfig/details/ https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230419/testrun/16369015/suite/build/test/gcc-12-defconfig/log Steps to reproduce: # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. # Original tuxmake command with fragments listed below. tuxmake --runtime podman --target-arch powerpc --toolchain gcc-12 --kconfig defconfig -- Linaro LKFT https://lkft.linaro.org
[PATCH 1/2] powerpc/64: Set default CPU in Kconfig
Following build regression started from next-20230131.
Regressions found on powerpc:
build/clang-nightly-tqm8xx_defconfig
build/clang-nightly-ppc64e_defconfig
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=powerpc
CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0
tqm8xx_defconfig
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=powerpc
CROSS_COMPILE=powerpc64le-linux-gnu- HOSTCC=clang CC=clang LLVM=1 LLVM_IAS=0
error: unknown target CPU '860'
note: valid target CPU values are: generic, 440, 450, 601, 602, 603, 603e,
603ev, 604, 604e, 620, 630, g3, 7400, g4, 7450, g4+, 750, 8548, 970, g5, a2,
e500, e500mc, e5500, power3, pwr3, power4, pwr4, power5, pwr5, power5x, pwr5x,
power6, pwr6, power6x, pwr6x, power7, pwr7, power8, pwr8, power9, pwr9,
power10, pwr10, powerpc, ppc, ppc32, powerpc64, ppc64, powerpc64le, ppc64le,
future
make[2]: *** [/builds/linux/scripts/Makefile.build:114:
scripts/mod/devicetable-offsets.s] Error 1
error: unknown target CPU '860'
note: valid target CPU values are: generic, 440, 450, 601, 602, 603, 603e,
603ev, 604, 604e, 620, 630, g3, 7400, g4, 7450, g4+, 750, 8548, 970, g5, a2,
e500, e500mc, e5500, power3, pwr3, power4, pwr4, power5, pwr5, power5x, pwr5x,
power6, pwr6, power6x, pwr6x, power7, pwr7, power8, pwr8, power9, pwr9,
power10, pwr10, powerpc, ppc, ppc32, powerpc64, ppc64, powerpc64le, ppc64le,
future
make[2]: *** [/builds/linux/scripts/Makefile.build:252: scripts/mod/empty.o]
Error 1
Reported-by: Linux Kernel Functional Testing
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230201/testrun/14479384/suite/build/test/clang-nightly-tqm8xx_defconfig/history/
The bisection pointed to this commit,
45f7091aac35 ("powerpc/64: Set default CPU in Kconfig")
--
Linaro LKFT
https://lkft.linaro.org
Re: [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
Hi Nathan,
On Mon, 23 Jan 2023 at 21:41, Nathan Chancellor wrote:
>
> Hi Naresh,
>
> On Mon, Jan 23, 2023 at 07:28:10PM +0530, Naresh Kamboju wrote:
> > FYI,
> > [ please provide comments, feedback and improvements on build/ ltp smoke
> > tests ]
> >
> > LKFT test farm have fetched your patch series [1]
> > [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
> > [1]
> > https://lore.kernel.org/llvm/20221228-drop-qunused-arguments-v2-0-9adbddd20...@kernel.org/
>
> Thank you a lot for testing this series, it is much appreciated!
>
> It looks like this was applied on top of 6.2-rc3 if I am reading your
> logs right but your mainline testing is recent, 6.2-rc5. I think the
> errors you are seeing here are just existing mainline regressions that
> were later fixed.
>
> > Following build warnings and errors reported.
> >
> > sh:
> > gcc-11-defconfig — FAIL
> > gcc-11-shx3_defconfig — FAIL
> > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221835/suite/build/tests/
> >
> > mainline getting passed.
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-defconfig/history/
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-shx3_defconfig/history/
> >
> > Build error:
> > In function 'follow_pmd_mask',
> > inlined from 'follow_pud_mask' at /builds/linux/mm/gup.c:735:9,
> > inlined from 'follow_p4d_mask' at /builds/linux/mm/gup.c:752:9,
> > inlined from 'follow_page_mask' at /builds/linux/mm/gup.c:809:9:
> > /builds/linux/include/linux/compiler_types.h:358:45: error: call to
> > '__compiletime_assert_263' declared with attribute error: Unsupported
> > access size for {READ,WRITE}_ONCE().
> > 358 | _compiletime_assert(condition, msg,
> > __compiletime_assert_, __COUNTER__)
>
> I think this was fixed with mainline commit 526970be53d5 ("sh/mm: Fix
> pmd_t for real"), released in 6.2-rc4. You can see a previous build
> failing in the same manner:
>
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc3-9-g5a41237ad1d4/testrun/14056384/suite/build/tests/
>
> > s390:
> > clang-15-defconfig — FAIL
> > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221913/suite/build/tests/
> >
> > mainline getting passed.
> > https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14300495/suite/build/test/clang-15-defconfig/history/
> >
> > Build error:
> > 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'
> > `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> > defined in discarded section `.exit.text' of fs/fuse/inode.o
> > `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> > defined in discarded section `.exit.text' of fs/fuse/inode.o
> > `.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
> > defined in discarded section `.exit.text' of crypto/algboss.o
> > `.exit.text' referenced in section `__bug_table' of drivers/scsi/sd.o:
> > defined in discarded section `.exit.text' of drivers/scsi/sd.o
> > `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> > defined in discarded section `.exit.text' of drivers/md/md.o
> > `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> > defined in discarded section `.exit.text' of drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > drivers/md/md.o: defined in discarded section `.exit.text' of
> > drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > drivers/md/md.o: defined in discarded section `.exit.text' of
> > drivers/md/md.o
> > `.exit.text' referenced in section `.altinstructions' of
> > net/iucv/iucv.o: defined in discarded section `.exit.text' of
> > net/iucv/iucv.o
> > `.exit.text' referenced in section `__bug_table' of
> > drivers/s390/cio/qdio_thinint.o: defined in discarded section
> > `.exit.text' of drivers/s390/cio/qdio_thinint.o
> > `.exit.text' referenced in section `__bug_table' of
> > drivers/s390/net/qeth_l3_main.o: defined in discarded section
> > `.exit
Re: [PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
+---
> arch/mips/loongson2ef/Platform | 2 +-
> arch/powerpc/Makefile | 2 +-
> arch/powerpc/kernel/vdso/Makefile | 25 +++--
> arch/s390/kernel/vdso64/Makefile| 4 +--
> arch/s390/purgatory/Makefile| 2 +-
> arch/x86/boot/compressed/Makefile | 2 +-
> drivers/gpu/drm/amd/display/dc/dml/Makefile | 3 ++-
> scripts/Kconfig.include | 2 +-
> scripts/Makefile.clang | 2 ++
> scripts/Makefile.compiler | 8 +++---
> scripts/as-version.sh | 2 +-
> 21 files changed, 74 insertions(+), 98 deletions(-)
FYI,
[ please provide comments, feedback and improvements on build/ ltp smoke tests ]
LKFT test farm have fetched your patch series [1]
[PATCH v2 00/14] Remove clang's -Qunused-arguments from KBUILD_CPPFLAGS
[1]
https://lore.kernel.org/llvm/20221228-drop-qunused-arguments-v2-0-9adbddd20...@kernel.org/
Following build warnings and errors reported.
sh:
gcc-11-defconfig — FAIL
gcc-11-shx3_defconfig — FAIL
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221835/suite/build/tests/
mainline getting passed.
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-defconfig/history/
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14298156/suite/build/test/gcc-11-shx3_defconfig/history/
Build error:
In function 'follow_pmd_mask',
inlined from 'follow_pud_mask' at /builds/linux/mm/gup.c:735:9,
inlined from 'follow_p4d_mask' at /builds/linux/mm/gup.c:752:9,
inlined from 'follow_page_mask' at /builds/linux/mm/gup.c:809:9:
/builds/linux/include/linux/compiler_types.h:358:45: error: call to
'__compiletime_assert_263' declared with attribute error: Unsupported
access size for {READ,WRITE}_ONCE().
358 | _compiletime_assert(condition, msg,
__compiletime_assert_, __COUNTER__)
s390:
clang-15-defconfig — FAIL
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/testrun/14221913/suite/build/tests/
mainline getting passed.
https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2-rc5/testrun/14300495/suite/build/test/clang-15-defconfig/history/
Build error:
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'
`.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
defined in discarded section `.exit.text' of fs/fuse/inode.o
`.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
defined in discarded section `.exit.text' of fs/fuse/inode.o
`.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
defined in discarded section `.exit.text' of crypto/algboss.o
`.exit.text' referenced in section `__bug_table' of drivers/scsi/sd.o:
defined in discarded section `.exit.text' of drivers/scsi/sd.o
`.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
defined in discarded section `.exit.text' of drivers/md/md.o
`.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
defined in discarded section `.exit.text' of drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
drivers/md/md.o: defined in discarded section `.exit.text' of
drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
drivers/md/md.o: defined in discarded section `.exit.text' of
drivers/md/md.o
`.exit.text' referenced in section `.altinstructions' of
net/iucv/iucv.o: defined in discarded section `.exit.text' of
net/iucv/iucv.o
`.exit.text' referenced in section `__bug_table' of
drivers/s390/cio/qdio_thinint.o: defined in discarded section
`.exit.text' of drivers/s390/cio/qdio_thinint.o
`.exit.text' referenced in section `__bug_table' of
drivers/s390/net/qeth_l3_main.o: defined in discarded section
`.exit.text' of drivers/s390/net/qeth_l3_main.o
`.exit.text' referenced in section `__bug_table' of
drivers/s390/net/qeth_l3_main.o: defined in discarded section
`.exit.text' of drivers/s390/net/qeth_l3_main.o
s390x-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion
fail ../../bfd/elf64-s390.c:3349
make[2]: *** [/builds/linux/scripts/Makefile.vmlinux:34: vmlinux] Error 1
But,
Build and boot pass on arm64, arm, x86_64 and i386.
Build test performed for mips, parisc, riscv, s390, sh, sparc and
powerpc (known build errors for maple_defconfig and cell_defconfig),
Please refer following link for detailed build, boot, LTP smoketest.
https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/https___lore_kernel_org_llvm_20221228-drop-qunused-arguments-v2-1-9adbddd20d86_kernel_org/?failures_only=false_layout=table#!#test-results
Best regards
Naresh Kamboju
--
Linaro LKFT
https://lkft.linaro.org
> ---
> base-commit: 88603b6dc419445847923fcb7fe5080067a30f98
> change-id: 20221228-drop-qunused-arguments-0c5c7dae54fb
>
> Best regards,
> --
> Nathan Chancellor
>
>
[next] powerpc: multiple definition of `____cacheline_aligned'; sound/core/oss/pcm_oss.o:(.bss+0x40): first defined here
Following powerpc builds failed on Linux next-20220428 and next-20220429. Regressions found on powerpc: - gcc-11-ppc64e_defconfig - gcc-10-ppc64e_defconfig - gcc-9-ppc64e_defconfig - gcc-8-ppc64e_defconfig - clang-14-ppc64e_defconfig - clang-nightly-ppc64e_defconfig - clang-13-ppc64e_defconfig Build error: - Error: Section .bss not empty in prom_init.c make[3]: *** [arch/powerpc/kernel/Makefile:191: arch/powerpc/kernel/prom_init_check] Error 1 make[3]: Target '__build' not remade because of errors. make[2]: *** [scripts/Makefile.build:595: arch/powerpc/kernel] Error 2 make[2]: Target '__build' not remade because of errors. make[1]: *** [Makefile:1996: arch/powerpc] Error 2 powerpc64le-linux-gnu-ld: sound/core/oss/pcm_plugin.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/oss/pcm_oss.o:(.bss+0x40): first defined here make[4]: *** [scripts/Makefile.build:530: sound/core/oss/snd-pcm-oss.o] Error 1 make[4]: Target '__build' not remade because of errors. make[3]: *** [scripts/Makefile.build:595: sound/core/oss] Error 2 powerpc64le-linux-gnu-ld: sound/core/seq/seq_clientmgr.o:(.bss+0x900): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_memory.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_queue.o:(.bss+0x140): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_fifo.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_timer.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_system.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_ports.o:(.bss+0x0): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here powerpc64le-linux-gnu-ld: sound/core/seq/seq_info.o:(.bss+0x40): multiple definition of `cacheline_aligned'; sound/core/seq/seq_lock.o:(.bss+0x0): first defined here make[4]: *** [scripts/Makefile.build:530: sound/core/seq/snd-seq.o] Error 1 make[4]: Target '__build' not remade because of errors. Reported-by: Linux Kernel Functional Testing steps to reproduce: --- # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch powerpc --toolchain gcc-11 --kconfig ppc64e_defconfig -- Linaro LKFT https://lkft.linaro.org [1] https://builds.tuxbuild.com/28Sn15hB2la1PweieGMLrUdbFMQ/
[next] powerpc: book3s_hv.c:4591:27: error: 'struct kvm_vcpu' has no member named 'wait'
[ Please ignore this email if it is already reported ] While building Linux next 20211214 powerpc defconfig with gcc-8/9/10/11 following warnings / errors noticed. make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- 'CC=sccache powerpc64le-linux-gnu-gcc' 'HOSTCC=sccache gcc' arch/powerpc/kvm/book3s_hv.c: In function 'kvmhv_run_single_vcpu': arch/powerpc/kvm/book3s_hv.c:4591:27: error: 'struct kvm_vcpu' has no member named 'wait' prepare_to_rcuwait(>wait); ^~ arch/powerpc/kvm/book3s_hv.c:4608:23: error: 'struct kvm_vcpu' has no member named 'wait' finish_rcuwait(>wait); ^~ make[3]: *** [scripts/Makefile.build:289: arch/powerpc/kvm/book3s_hv.o] Error 1 meta data: --- git describe: next-20211214 git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git_sha: 0bafb8f3ebc84525d0ae0fcea22d12151b99312f git_short_log: 0bafb8f3ebc8 (\"Add linux-next specific files for 20211214\") target_arch: powerpc toolchain: gcc-8 steps to reproduce: # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch powerpc --toolchain gcc-8 --kconfig defconfig Reported-by: Linux Kernel Functional Testing build log: https://builds.tuxbuild.com/22IPCvkz8z9pqpgCMPoNw7OstPD/ -- Linaro LKFT https://lkft.linaro.org
powerpc: pervasive.c:: error: unannotated fall-through between switch labels
Regression found on ppc clang-nightly build. Following build warnings / errors reported on linux next 2027. metadata: git_describe: next-2027 git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git_short_log: fd96a4057bd0 (\"Add linux-next specific files for 2027\") target_arch: ppc toolchain: clang-nightly build error : -- :1559:2: warning: syscall futex_waitv not implemented [-W#warnings] #warning syscall futex_waitv not implemented ^ 1 warning generated. arch/powerpc/platforms/cell/pervasive.c:81:2: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough] case SRR1_WAKEEE: ^ arch/powerpc/platforms/cell/pervasive.c:81:2: note: insert 'break;' to avoid fall-through case SRR1_WAKEEE: ^ break; 1 error generated. Reported-by: Linux Kernel Functional Testing build link: --- https://builds.tuxbuild.com/211sfsuxt3flikHFzRts8cFUwqe/build.log build config: - https://builds.tuxbuild.com/211sfsuxt3flikHFzRts8cFUwqe/config # To install tuxmake on your system globally # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch powerpc --toolchain clang-nightly --kconfig defconfig LLVM_IAS=0 -- Linaro LKFT https://lkft.linaro.org
powerpc: mcu_mpc8349emitx.c:189:13: error: unused variable 'ret' [-Werror=unused-variable]
[Please ignore this email if it is already reported ] Regression found on powerpc gcc-8/9/10 and gcc-11 built with ppc6xx_defconfig Following build warnings / errors reported on linux next 20211109. metadata: git_describe: next-20211109 git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git_short_log: c8109c2ba35e (\"Add linux-next specific files for 20211109\") target_arch: powerpc toolchain: gcc-11 build error : -- :1559:2: warning: #warning syscall futex_waitv not implemented [-Wcpp] arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c: In function 'mcu_remove': arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c:189:13: error: unused variable 'ret' [-Werror=unused-variable] 189 | int ret; | ^~~ cc1: all warnings being treated as errors make[4]: *** [scripts/Makefile.build:288: arch/powerpc/platforms/83xx/mcu_mpc8349emitx.o] Error 1 make[4]: Target '__build' not remade because of errors. make[3]: *** [scripts/Makefile.build:571: arch/powerpc/platforms/83xx] Error 2 Reported-by: Linux Kernel Functional Testing build link: --- https://builds.tuxbuild.com/20fICxLPRCpcISasoGwKGICBELv/build.log build config: - https://builds.tuxbuild.com/20fICxLPRCpcISasoGwKGICBELv/config # To install tuxmake on your system globally # sudo pip3 install -U tuxmake tuxmake --runtime podman --target-arch powerpc --toolchain gcc-11 --kconfig ppc6xx_defconfig -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 5.4 00/52] 5.4.153-rc2 review
On Tue, 12 Oct 2021 at 12:16, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.153 release.
> There are 52 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 Oct 2021 06:44:25 +.
> 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.4.153-rc2.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.4.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
stable rc 5.4.153-rc2 Powerpc build failed.
In file included from arch/powerpc/net/bpf_jit64.h:11,
from arch/powerpc/net/bpf_jit_comp64.c:19:
arch/powerpc/net/bpf_jit_comp64.c: In function 'bpf_jit_build_body':
arch/powerpc/net/bpf_jit.h:32:9: error: expected expression before 'do'
32 | do { if (d) { (d)[idx] = instr; } idx++; } while (0)
| ^~
arch/powerpc/net/bpf_jit.h:33:33: note: in expansion of macro 'PLANT_INSTR'
33 | #define EMIT(instr) PLANT_INSTR(image, ctx->idx, instr)
| ^~~
arch/powerpc/net/bpf_jit_comp64.c:415:41: note: in expansion of macro 'EMIT'
415 | EMIT(PPC_LI(dst_reg, 0));
| ^~~~
arch/powerpc/net/bpf_jit.h:33:33: note: in expansion of macro 'PLANT_INSTR'
33 | #define EMIT(instr) PLANT_INSTR(image, ctx->idx, instr)
| ^~~
arch/powerpc/net/bpf_jit.h:41:33: note: in expansion of macro 'EMIT'
41 | #define PPC_ADDI(d, a, i) EMIT(PPC_INST_ADDI |
___PPC_RT(d) | \
| ^~~~
arch/powerpc/net/bpf_jit.h:44:33: note: in expansion of macro 'PPC_ADDI'
44 | #define PPC_LI(r, i)PPC_ADDI(r, 0, i)
| ^~~~
arch/powerpc/net/bpf_jit_comp64.c:415:46: note: in expansion of macro 'PPC_LI'
415 | EMIT(PPC_LI(dst_reg, 0));
| ^~
make[3]: *** [scripts/Makefile.build:262:
arch/powerpc/net/bpf_jit_comp64.o] Error 1
make[3]: Target '__build' not remade because of errors.
Reported-by: Linux Kernel Functional Testing
--
Linaro LKFT
https://lkft.linaro.org
[next] [powerpc] tau_6xx.c:204:30: error: too many arguments for format [-Werror=format-extra-args]
While building Linux next-20210610 following builds failed due to
these warnings / errors.
- powerpc (ppc6xx_defconfig) with gcc-8
- powerpc (ppc6xx_defconfig) with gcc-9
- powerpc (ppc6xx_defconfig) with gcc-10
arch/powerpc/kernel/tau_6xx.c: In function 'TAU_init':
arch/powerpc/kernel/tau_6xx.c:204:30: error: too many arguments for
format [-Werror=format-extra-args]
tau_workq = alloc_workqueue("tau", WQ_UNBOUND, 1, 0);
^
cc1: all warnings being treated as errors
Reported-by: Naresh Kamboju
steps to reproduce:
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds across a variety of
# architectures, toolchains, kernel configurations, and make targets.
#
# TuxMake supports the concept of runtimes.
# See https://docs.tuxmake.org/runtimes/, for that to work it requires
# that you install podman or docker on your system.
#
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
tuxmake --runtime podman --target-arch powerpc --toolchain gcc-9
--kconfig ppc6xx_defconfig
ref:
https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/1334701929#L116
--
Linaro LKFT
https://lkft.linaro.org
Re : mm/mremap: use range flush that does TLB and page walk cache flush
The LKFT build system detected these build warnings and errors. Regressions found on parisc: - build/gcc-9-defconfig - build/gcc-9-tinyconfig - build/gcc-10-allnoconfig - build/gcc-10-tinyconfig - build/gcc-9-allnoconfig - build/gcc-10-defconfig make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=parisc CROSS_COMPILE=hppa-linux-gnu- 'CC=sccache hppa-linux-gnu-gcc' 'HOSTCC=sccache gcc' In file included from /builds/linux/arch/parisc/include/asm/cacheflush.h:7, from /builds/linux/include/linux/highmem.h:12, from /builds/linux/include/linux/pagemap.h:11, from /builds/linux/include/linux/ksm.h:13, from /builds/linux/mm/mremap.c:14: /builds/linux/mm/mremap.c: In function 'flush_pte_tlb_pwc_range': /builds/linux/arch/parisc/include/asm/tlbflush.h:20:2: error: 'return' with a value, in function returning void [-Werror=return-type] 20 | __flush_tlb_range((vma)->vm_mm->context, start, end) | ^~~~ /builds/linux/mm/mremap.c:219:9: note: in expansion of macro 'flush_tlb_range' 219 | return flush_tlb_range(vma, start, end); | ^~~ /builds/linux/mm/mremap.c:214:33: note: declared here 214 | #define flush_pte_tlb_pwc_range flush_pte_tlb_pwc_range | ^~~ /builds/linux/mm/mremap.c:215:20: note: in expansion of macro 'flush_pte_tlb_pwc_range' 215 | static inline void flush_pte_tlb_pwc_range(struct vm_area_struct *vma, |^~~ cc1: some warnings being treated as errors make[2]: *** [/builds/linux/scripts/Makefile.build:273: mm/mremap.o] Error 1 Reported-by: Naresh Kamboju steps to reproduce: --- #!/bin/sh # TuxMake is a command line tool and Python library that provides # portable and repeatable Linux kernel builds across a variety of # architectures, toolchains, kernel configurations, and make targets. # # TuxMake supports the concept of runtimes. # See https://docs.tuxmake.org/runtimes/, for that to work it requires # that you install podman or docker on your system. # # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. tuxmake --runtime podman --target-arch parisc --toolchain gcc-9 --kconfig allnoconfig -- Linaro LKFT https://lkft.linaro.org
Clang: powerpc: kvm/book3s_hv_nested.c:264:6: error: stack frame size of 2480 bytes in function 'kvmhv_enter_nested_guest'
Linux mainline master build breaks for powerpc defconfig. There are multiple errors / warnings with clang-12 and clang-11 and 10. - powerpc (defconfig) with clang-12 - powerpc (defconfig) with clang-11 - powerpc (defconfig) with clang-10 The following build errors / warnings triggered with clang-12. make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp LLVM=1 ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache clang' /builds/linux/arch/powerpc/kvm/book3s_hv_nested.c:264:6: error: stack frame size of 2480 bytes in function 'kvmhv_enter_nested_guest' [-Werror,-Wframe-larger-than=] long kvmhv_enter_nested_guest(struct kvm_vcpu *vcpu) ^ 1 error generated. make[3]: *** [/builds/linux/scripts/Makefile.build:271: arch/powerpc/kvm/book3s_hv_nested.o] Error 1 Reported-by: Naresh Kamboju The following build errors / warnings triggered with clang-10 and clang-11. - powerpc (defconfig) with clang-11 - powerpc (defconfig) with clang-10 make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp LLVM=1 ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache clang' /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/sigtramp.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/sigtramp.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/gettimeofday.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/gettimeofday.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/datapage.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/datapage.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/cacheflush.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/cacheflush.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/note.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/note.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/getcpu.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/getcpu.o /usr/bin/powerpc64le-linux-gnu-ld: arch/powerpc/kernel/vdso32/vgettimeofday.o: compiled for a little endian system and target is big endian /usr/bin/powerpc64le-linux-gnu-ld: failed to merge target specific data of file arch/powerpc/kernel/vdso32/vgettimeofday.o clang: error: unable to execute command: Segmentation fault (core dumped) clang: error: linker command failed due to signal (use -v to see invocation) make[2]: *** [/builds/linux/arch/powerpc/kernel/vdso32/Makefile:51: arch/powerpc/kernel/vdso32/vdso32.so.dbg] Error 254 make[2]: Target 'include/generated/vdso32-offsets.h' not remade because of errors. Reported-by: Naresh Kamboju build link, https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline/-/jobs/1110841371#L59 -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 18/20] block: refator submit_bio_noacct
On Thu, 2 Jul 2020 at 20:45, Christoph Hellwig wrote:
>
> On Thu, Jul 02, 2020 at 10:10:10AM -0400, Qian Cai wrote:
> > On Mon, Jun 29, 2020 at 09:39:45PM +0200, Christoph Hellwig wrote:
> > > Split out a __submit_bio_noacct helper for the actual de-recursion
> > > algorithm, and simplify the loop by using a continue when we can't
> > > enter the queue for a bio.
> > >
> > > Signed-off-by: Christoph Hellwig
> >
> > Reverting this commit and its dependencies,
> >
> > 5a6c35f9af41 block: remove direct_make_request
> > ff93ea0ce763 block: shortcut __submit_bio_noacct for blk-mq drivers
> >
> > fixed the stack-out-of-bounds during boot,
> >
> > https://lore.kernel.org/linux-block/bcdeaa05a9728...@google.com/
>
> Yikes. bio_alloc_bioset pokes into bio_list[1] in a totally
> undocumented way. But even with that the problem should only show
> up with "block: shortcut __submit_bio_noacct for blk-mq drivers".
>
> Can you try this patch?
Applied your patch on top of linux-next 20200702 and tested on
arm64 and x86_64 devices and the reported BUG fixed.
Reported-by: Naresh Kamboju
Tested-by: Naresh Kamboju
>
> diff --git a/block/blk-core.c b/block/blk-core.c
> index bf882b8d84450c..9f1bf8658b611a 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -1155,11 +1155,10 @@ static blk_qc_t __submit_bio_noacct(struct bio *bio)
> static blk_qc_t __submit_bio_noacct_mq(struct bio *bio)
> {
> struct gendisk *disk = bio->bi_disk;
> - struct bio_list bio_list;
> + struct bio_list bio_list[2] = { };
> blk_qc_t ret = BLK_QC_T_NONE;
>
> - bio_list_init(_list);
> - current->bio_list = _list;
> + current->bio_list = bio_list;
>
> do {
> WARN_ON_ONCE(bio->bi_disk != disk);
> @@ -1174,7 +1173,7 @@ static blk_qc_t __submit_bio_noacct_mq(struct bio *bio)
> }
>
> ret = blk_mq_submit_bio(bio);
> - } while ((bio = bio_list_pop(_list)));
> + } while ((bio = bio_list_pop(_list[0])));
>
> current->bio_list = NULL;
> return ret;
ref:
https://lkft.validation.linaro.org/scheduler/job/1538359#L288
https://lkft.validation.linaro.org/scheduler/job/1538360#L572
- Naresh
Re: [PATCH 18/20] block: refator submit_bio_noacct
On Thu, 2 Jul 2020 at 19:40, Qian Cai wrote: > > On Mon, Jun 29, 2020 at 09:39:45PM +0200, Christoph Hellwig wrote: > > Split out a __submit_bio_noacct helper for the actual de-recursion > > algorithm, and simplify the loop by using a continue when we can't > > enter the queue for a bio. > > > > Signed-off-by: Christoph Hellwig Kernel BUG: on arm64 and x86_64 devices running linux next-rc3-next-20200702 with KASAN config enabled. While running mkfs -t ext4. metadata: git branch: master git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git git commit: d37d57041350dff35dd17cbdf9aef4011acada38 git describe: next-20200702 make_kernelversion: 5.8.0-rc3 kernel-config: https://builds.tuxbuild.com/DnjQHvYrx586eUoFxtYZxQ/kernel.config steps to reproduce: # mkfs -t ext4 /dev/disk/by-id/ata-SanDisk_SDSSDA120G_165193445014 BUG: KASAN: stack-out-of-bounds in bio_alloc_bioset+0x28c/0x2c8 [ 59.398307] Read of size 8 at addr 0009084277e0 by task mkfs.ext4/417 [ 59.405121] [ 59.406644] CPU: 5 PID: 417 Comm: mkfs.ext4 Not tainted 5.8.0-rc3-next-20200702 #1 [ 59.414248] Hardware name: ARM Juno development board (r2) (DT) [ 59.420195] Call trace: [ 59.422683] dump_backtrace+0x0/0x2b8 [ 59.426386] show_stack+0x18/0x28 [ 59.429741] dump_stack+0xec/0x144 [ 59.433183] print_address_description.isra.0+0x6c/0x448 [ 59.438531] kasan_report+0x134/0x200 [ 59.442226] __asan_load8+0x9c/0xd8 [ 59.445751] bio_alloc_bioset+0x28c/0x2c8 [ 59.449796] bio_clone_fast+0x28/0x98 [ 59.453492] bio_split+0x64/0x138 [ 59.456842] __blk_queue_split+0x534/0x698 [ 59.460979] blk_mq_submit_bio+0x10c/0x680 [ 59.465118] submit_bio_noacct+0x57c/0x640 [ 59.469253] submit_bio+0xc0/0x358 [ 59.472688] submit_bio_wait+0xc0/0x110 [ 59.476561] blkdev_issue_discard+0xd0/0x138 [ 59.480877] blk_ioctl_discard+0x1b8/0x238 [ 59.485008] blkdev_common_ioctl+0x594/0xd38 [ 59.489312] blkdev_ioctl+0x130/0x578 [ 59.493010] block_ioctl+0x78/0x98 [ 59.496453] ksys_ioctl+0xb8/0xf8 [ 59.499808] __arm64_sys_ioctl+0x44/0x60 [ 59.503781] el0_svc_common.constprop.0+0xa4/0x1e0 [ 59.508615] do_el0_svc+0x38/0xa0 [ 59.511967] el0_sync_handler+0x98/0x1a8 [ 59.515922] el0_sync+0x158/0x180 [ 59.519255] [ 59.520761] The buggy address belongs to the page: [ 59.525590] page:fe00240109c0 refcount:0 mapcount:0 mapping: index:0x0 [ 59.533895] flags: 0x2000() [ 59.537779] raw: 2000 fe00240109c8 [ 59.545575] raw: [ 59.553352] page dumped because: kasan: bad access detected [ 59.558947] [ 59.560463] addr 0009084277e0 is located in stack of task mkfs.ext4/417 at offset 48 in frame: [ 59.569475] submit_bio_noacct+0x0/0x640 [ 59.573423] [ 59.574930] this frame has 2 objects: [ 59.578624] [32, 48) 'bio_list' [ 59.578644] [64, 96) 'bio_list_on_stack' [ 59.581889] [ 59.587412] Memory state around the buggy address: [ 59.592243] 000908427680: 00 00 00 f2 00 00 00 f2 f2 f2 00 00 00 00 00 f3 [ 59.599510] 000908427700: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 [ 59.606777] >000908427780: 00 00 00 00 00 00 f1 f1 f1 f1 00 00 f2 f2 00 00 [ 59.614031]^ [ 59.620427] 000908427800: 00 00 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 [ 59.627694] 000908427880: 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00 f3 f3 [ 59.634946] == [ 59.642198] Disabling lock debugging due to kernel taint Kernel BUG on x86_64: [ 17.809563] == [ 17.816786] BUG: KASAN: stack-out-of-bounds in bio_alloc_bioset+0x31f/0x340 [ 17.823750] Read of size 8 at addr 888225f9f450 by task systemd-udevd/361 [ 17.830881] [ 17.832384] CPU: 0 PID: 361 Comm: systemd-udevd Not tainted 5.8.0-rc3-next-20200702 #1 [ 17.840294] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.2 05/23/2018 [ 17.847686] Call Trace: [ 17.850143] dump_stack+0x84/0xba [ 17.853462] print_address_description.constprop.0+0x1f/0x210 [ 17.859212] ? _raw_spin_lock_irqsave+0x7c/0xd0 [ 17.859214] ? _raw_write_lock_irqsave+0xd0/0xd0 [ 17.859217] ? bio_alloc_bioset+0x31f/0x340 [ 17.859220] kasan_report.cold+0x37/0x7c [ 17.859222] ? bio_alloc_bioset+0x31f/0x340 [ 17.859224] __asan_load8+0x86/0xb0 [ 17.859226] bio_alloc_bioset+0x31f/0x340 [ 17.859228] ? bvec_alloc+0x160/0x160 [ 17.859230] ? bio_alloc_bioset+0x253/0x340 [ 17.859232] ? mpage_alloc.isra.0+0x37/0x120 [ 17.859234] ? do_mpage_readpage+0x740/0xd40 [ 17.859236] ? mpage_readahead+0x196/0x280 [ 17.859238] ? blkdev_readahead+0x10/0x20 [ 17.859241] ? read_pages+0x149/0x470 [ 17.859243] ?
Re: [PATCH] crypto: af_alg - Fix regression on empty requests
On Fri, 26 Jun 2020 at 12:00, Herbert Xu wrote: > > On Tue, Jun 23, 2020 at 10:02:17AM -0700, Eric Biggers wrote: > > > > The source code for the two failing AF_ALG tests is here: > > > > https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/crypto/af_alg02.c > > https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/crypto/af_alg05.c > > > > They use read() and write(), not send() and recv(). > > > > af_alg02 uses read() to read from a "salsa20" request socket without writing > > anything to it. It is expected that this returns 0, i.e. that behaves like > > encrypting an empty message. Since we are on this subject, LTP af_alg02 test case fails on stable 4.9 and stable 4.4 This is not a regression because the test case has been failing from the beginning. Is this test case expected to fail on stable 4.9 and 4.4 ? or any chance to fix this on these older branches ? Test output: af_alg02.c:52: BROK: Timed out while reading from request socket. ref: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.228-191-g082e807235d7/testrun/2884917/suite/ltp-crypto-tests/test/af_alg02/history/ https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.228-191-g082e807235d7/testrun/2884606/suite/ltp-crypto-tests/test/af_alg02/log - Naresh
Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc
On Wed, 3 Jun 2020 at 19:03, Joerg Roedel wrote: > > On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > > @Joerg, Could you please have a look? > > Can you please try the attached patch? @Joerg, Linaro test farm noticed this kernel crash on nxp ls2088 Machine model: Freescale Layerscape 2088A RDB Board while booting Linux mainline 5.7.0 version kernel. After applying your proposed patch fixed boot problem. Tested-by: Naresh Kamboju Test ref: https://lavalab.nxp.com/scheduler/job/23787#L426 Here is the kernel crash log before patch applied, [0.00] Linux version 5.7.0-03887-gf6aee505c71b (TuxBuild@ecb9ef34f06f) (gcc version 9.3.0 (Debian 9.3.0-8), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP PREEMPT Wed Jun 3 18:21:26 UTC 2020 [0.00] Machine model: Freescale Layerscape 2088A RDB Board <> [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [0.00] Unable to handle kernel paging request at virtual address fffe8000 [0.00] Mem abort info: [0.00] ESR = 0x9604 [0.00] EC = 0x25: DABT (current EL), IL = 32 bits [0.00] SET = 0, FnV = 0 [0.00] EA = 0, S1PTW = 0 [0.00] Data abort info: [0.00] ISV = 0, ISS = 0x0004 [0.00] CM = 0, WnR = 0 [0.00] [fffe8000] address between user and kernel address ranges [0.00] Internal error: Oops: 9604 [#1] PREEMPT SMP [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.7.0-03887-gf6aee505c71b #1 [0.00] Hardware name: Freescale Layerscape 2088A RDB Board (DT) [0.00] pstate: 8085 (Nzcv daIf -PAN -UAO BTYPE=--) [0.00] pc : map_kernel_range_noflush+0xc0/0x280 [0.00] lr : __vmalloc_node_range+0x154/0x2a0 [0.00] sp : b3b1dcbc3e20 [0.00] x29: b3b1dcbc3e20 x28: fffe8000 [0.00] x27: 800010004000 x26: 80001000 [0.00] x25: 00402dc2 x24: b3b1dc53c000 [0.00] x23: 00680f13 x22: 0004 [0.00] x21: b3b1dc53cf48 x20: [0.00] x19: b3b1dc627800 x18: 00c0 [0.00] x17: x16: 0007 [0.00] x15: dead0100 x14: fe020b990600 [0.00] x13: dead0122 x12: 0001 [0.00] x11: x10: 0082fe3fdec0 [0.00] x9 : 0082fe342d58 x8 : 4cd121ba5000 [0.00] x7 : 80801000 x6 : 0004 [0.00] x5 : fffd x4 : 4000 [0.00] x3 : 80005000 x2 : 00018000 [0.00] x1 : x0 : 800010003fff [0.00] Call trace: [0.00] map_kernel_range_noflush+0xc0/0x280 [0.00] __vmalloc_node_range+0x154/0x2a0 [0.00] __vmalloc_node+0x5c/0x70 [0.00] init_IRQ+0xac/0xf8 [0.00] start_kernel+0x2d0/0x4dc [0.00] Code: f90047e0 d503201f d2a80003 8b030343 (f9400380) [0.00] random: get_random_bytes called from print_oops_end_marker+0x2c/0x58 with crng_init=0 [0.00] ---[ end trace ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! ref: https://lavalab.nxp.com/scheduler/job/23596#L603 -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH net 11/16] net: ethernet: marvell: mvneta: fix fixed-link phydev leaks
On Thu, 7 May 2020 at 16:43, Greg Kroah-Hartman
wrote:
>
> > >
> > > Greg, 3f65047c853a ("of_mdio: add helper to deregister fixed-link
> > > PHYs") needs to be backported as well for these.
> > >
> > > Original series can be found here:
> > >
> > >
> > > https://lkml.kernel.org/r/1480357509-28074-1-git-send-email-jo...@kernel.org
> >
> > Ah, thanks for that, I thought I dropped all of the ones that caused
> > build errors, but missed the above one. I'll go take the whole series
> > instead.
>
> This should now all be fixed up, thanks.
While building kernel Image for arm architecture on stable-rc 4.4 branch
the following build error found.
of_mdio: add helper to deregister fixed-link PHYs
commit 3f65047c853a2a5abcd8ac1984af3452b5df4ada upstream.
Add helper to deregister fixed-link PHYs registered using
of_phy_register_fixed_link().
Convert the two drivers that care to deregister their fixed-link PHYs to
use the new helper, but note that most drivers currently fail to do so.
Signed-off-by: Johan Hovold
Signed-off-by: David S. Miller
[only take helper function for 4.4.y - gregkh]
# make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=gcc CC="sccache
arm-linux-gnueabihf-gcc" O=build zImage
70 #
71 ../drivers/of/of_mdio.c: In function ‘of_phy_deregister_fixed_link’:
72 ../drivers/of/of_mdio.c:379:2: error: implicit declaration of
function ‘fixed_phy_unregister’; did you mean ‘fixed_phy_register’?
[-Werror=implicit-function-declaration]
73 379 | fixed_phy_unregister(phydev);
74 | ^~~~
75 | fixed_phy_register
76 ../drivers/of/of_mdio.c:381:22: error: ‘struct phy_device’ has no
member named ‘mdio’; did you mean ‘mdix’?
77 381 | put_device(>mdio.dev); /* of_phy_find_device() */
78 | ^~~~
79 | mdix
>
> greg k-h
Re: [PATCH net 11/16] net: ethernet: marvell: mvneta: fix fixed-link phydev leaks
On Tue, 29 Nov 2016 at 00:00, Johan Hovold wrote:
>
> Make sure to deregister and free any fixed-link PHY registered using
> of_phy_register_fixed_link() on probe errors and on driver unbind.
>
> Fixes: 83895bedeee6 ("net: mvneta: add support for fixed links")
> Signed-off-by: Johan Hovold
> ---
> drivers/net/ethernet/marvell/mvneta.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/ethernet/marvell/mvneta.c
> b/drivers/net/ethernet/marvell/mvneta.c
> index 0c0a45af950f..707bc4680b9b 100644
> --- a/drivers/net/ethernet/marvell/mvneta.c
> +++ b/drivers/net/ethernet/marvell/mvneta.c
> @@ -4191,6 +4191,8 @@ static int mvneta_probe(struct platform_device *pdev)
> clk_disable_unprepare(pp->clk);
> err_put_phy_node:
> of_node_put(phy_node);
> + if (of_phy_is_fixed_link(dn))
> + of_phy_deregister_fixed_link(dn);
While building kernel Image for arm architecture on stable-rc 4.4 branch
the following build error found.
drivers/net/ethernet/marvell/mvneta.c:3442:3: error: implicit
declaration of function 'of_phy_deregister_fixed_link'; did you mean
'of_phy_register_fixed_link'? [-Werror=implicit-function-declaration]
|of_phy_deregister_fixed_link(dn);
|^~~~
|of_phy_register_fixed_link
ref:
https://gitlab.com/Linaro/lkft/kernel-runs/-/jobs/541374729
- Naresh
