From: Nathan Chancellor <nathan@kernel.org>
To: ci_notify@linaro.org
Cc: Arnd Bergmann <arnd@arndb.de>, llvm@lists.linux.dev, arnd@linaro.org
Subject: Re: [TCWG CI] Failure after v6.1.8-105-gf5e58b546cbe: drm/panfrost: fix GENERIC_ATOMIC64 dependency
Date: Mon, 6 Feb 2023 09:43:49 -0700 [thread overview]
Message-ID: <Y+EuRS3YDD8XbHgo@dev-arch.thelio-3990X> (raw)
In-Reply-To: <1896363883.10092.1675654927497@jenkins.jenkins>
Hi,
On Mon, Feb 06, 2023 at 03:42:06AM +0000, ci_notify@linaro.org wrote:
> Failure after v6.1.8-105-gf5e58b546cbe: drm/panfrost: fix GENERIC_ATOMIC64 dependency:
>
> Results changed to
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 23010
> # First few build errors in logs:
> # 00:31:22 ./include/linux/fortify-string.h:543:4: error: call to '__read_overflow' declared with 'error' attribute: detected read beyond size of object (1st parameter)
> # 00:31:23 make[4]: *** [scripts/Makefile.build:250: drivers/infiniband/core/cma.o] Error 1
> # 00:31:55 make[3]: *** [scripts/Makefile.build:500: drivers/infiniband/core] Error 2
> # 00:31:55 make[2]: *** [scripts/Makefile.build:500: drivers/infiniband] Error 2
> # 00:32:29 make[1]: *** [scripts/Makefile.build:500: drivers] Error 2
> # 00:32:29 make: *** [Makefile:2005: .] Error 2
>
> from
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 23021
>
> THIS IS THE END OF INTERESTING STUFF. BELOW ARE LINKS TO BUILDS, REPRODUCTION INSTRUCTIONS, AND THE RAW COMMIT.
>
> For latest status see comments in https://linaro.atlassian.net/browse/LLVM-647 .
> Status of v6.1.8-105-gf5e58b546cbe commit for tcwg_kernel:
> commit f5e58b546cbe76f049df97570cf0580aaaf3f900
> Author: Arnd Bergmann <arnd@arndb.de>
> Date: Tue Jan 17 17:44:43 2023 +0100
>
> drm/panfrost: fix GENERIC_ATOMIC64 dependency
>
> [ Upstream commit 6437a549ae178a3f5a5c03e983f291ebcdc2bbc7 ]
>
> On ARMv5 and earlier, a randconfig build can still run into
>
> WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE
> Depends on [n]: IOMMU_SUPPORT [=y] && (ARM [=y] || ARM64 || COMPILE_TEST [=y]) && !GENERIC_ATOMIC64 [=y]
> Selected by [y]:
> - DRM_PANFROST [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARM [=y] || ARM64 || COMPILE_TEST [=y] && !GENERIC_ATOMIC64 [=y]) && MMU [=y]
>
> Rework the dependencies to always require a working cmpxchg64.
>
> Fixes: db594ba3fcf9 ("drm/panfrost: depend on !GENERIC_ATOMIC64 when using COMPILE_TEST")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Reviewed-by: Steven Price <steven.price@arm.com>
> Signed-off-by: Steven Price <steven.price@arm.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20230117164456.1591901-1-arnd@kernel.org
> Signed-off-by: Sasha Levin <sashal@kernel.org>
Not an issue with this patch, it is a compiler issue:
https://github.com/ClangBuiltLinux/linux/issues/1687
A recent change in LLVM made this failure more likely but it has been
around for a while in certain configurations. I am guessing the
bisection landed on this change because it fixes one problem while
exposing another.
Cheers,
Nathan
prev parent reply other threads:[~2023-02-06 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 3:42 [TCWG CI] Failure after v6.1.8-105-gf5e58b546cbe: drm/panfrost: fix GENERIC_ATOMIC64 dependency ci_notify
2023-02-06 16:43 ` Nathan Chancellor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+EuRS3YDD8XbHgo@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@linaro.org \
--cc=ci_notify@linaro.org \
--cc=llvm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.