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]
Message-ID: <15979303.uLZWGnKmhe@diego>
Date: Tue, 10 Jun 2025 13:21:57 +0200
From: Heiko StĂĽbner <heiko@...ech.de>
To: open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
 Linux ARM <linux-arm-kernel@...ts.infradead.org>,
 Linux Regressions <regressions@...ts.linux.dev>,
 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
 <devicetree@...r.kernel.org>, Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Peter Robinson <pbrobinson@...il.com>, krzk+dt@...nel.org,
 Dan Carpenter <dan.carpenter@...aro.org>,
 Andrew Morton <akpm@...ux-foundation.org>, Arnd Bergmann <arnd@...db.de>,
 Rob Herring <robh@...nel.org>
Subject:
 Re: next-20250610: arm64 No rule to make target rockchip
 rk3399-rockpro64-screen.dtso

Hi Naresh,

Am Dienstag, 10. Juni 2025, 12:25:31 Mitteleuropäische Sommerzeit schrieb Naresh Kamboju:
> Regression while building arm64 with the Linux next-20250610
> the following dtb build errors noticed.
> 
> Regressions found on arm64 builds
> - dtb build error
> 
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
> 
> First seen on the next-20250610
> Good: next-20250606
> Bad:  next-20250610
> 
> Anders bisected this to,
> # first bad commit:
>   [49760b9f60528393cca3ea35c4d0719f84215a48]
>   arm64: dts: rockchip: add overlay for RockPro64 screen
> 
> Build regression: arm64 No rule to make target rockchip
> rk3399-rockpro64-screen.dtso
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> ## Build error
> *** No rule to make target
> 'arch/arm64/boot/dts/rockchip/rk3399-rockpro64-screen.dtso', needed by
> '__dtbs_install'.
> 
> ## Source
> * Kernel version: 6.16.0-rc1
> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> * Git sha:  b27cc623e01be9de1580eaa913508b237a7a9673
> * git describe: next-20250610
> * Toolchains: gcc-8, gcc-13, clang-20
> * Config: defconfig
> * Architecture: arm64
> 
> ## Build details
> * Build warning:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/build.log
> * Build link:  https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/config

thanks a lot for this notification.

I'm surprised that overlay build at all when I built it yesterday.
But yeah, the dtbs_install target really broke with that change.

I've amended the commit now [0], to change dtso to dtbo and ran the
dtbs_install target sucessfully with that change.

So on the next linux-next creation, this should hopefully be gone.


Heiko

[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v6.17-armsoc/dts64&id=e14491aaa6ff598bbe9d462e44c01ac65754f445



> 
> ## Steps to reproduce
>  - tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13
> --kconfig defconfig
> 
> --
> Linaro LKFT
> https://lkft.linaro.org
> 





Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ