From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, X86 ML <x86@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: clang-12: tun: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err -2)
Date: Mon, 22 Feb 2021 12:37:49 -0700 [thread overview]
Message-ID: <20210222193749.GA2954@24bbad8f3778> (raw)
In-Reply-To: <CA+G9fYuE4ELVDju=LESHnphL4Z2DT5YQjdh9rNgr5D1x5gZxgg@mail.gmail.com>
On Tue, Feb 23, 2021 at 01:01:16AM +0530, Naresh Kamboju wrote:
> Following test regressions reported after upgrade to clang-12 from clang-10.
> Regression detected on Linux mainline and stable-rc 5.4, 5.10 and 5.11.
>
> qemu-x86_64-clang-12 failed test cases,
> ltp-containers-tests:
> * netns_breakns_ip_ipv4_ioctl
> * netns_breakns_ip_ipv4_netlink
> * netns_breakns_ip_ipv6_ioctl
> * netns_breakns_ip_ipv6_netlink
> * netns_breakns_ns_exec_ipv4_ioctl
> * netns_breakns_ns_exec_ipv4_netlink
> * netns_breakns_ns_exec_ipv6_ioctl
> * netns_breakns_ns_exec_ipv6_netlink
> * netns_comm_ip_ipv4_ioctl
> * netns_comm_ip_ipv4_netlink
> * netns_comm_ip_ipv6_ioctl
> * netns_comm_ip_ipv6_netlink
> * netns_comm_ns_exec_ipv4_ioctl
> * netns_comm_ns_exec_ipv4_netlink
> * netns_comm_ns_exec_ipv6_ioctl
> * netns_comm_ns_exec_ipv6_netlink
> * netns_netlink
>
> Test error log:
> --------------
> [ 19.017163] tun: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err -2)
> open: No such device
> netns_netlink 1 TBROK : netns_netlink.c:143: system() failed
> netns_netlink 2 TBROK : netns_netlink.c:143: Remaining cases broken
> netns_breakns 1 TINFO: timeout per run is 0h 15m 0s
> [ 19.070922] veth: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err -2)
> [ 19.095171] veth: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err -2)
> Error: Unknown device type.[ 19.101364] ip (751) used greatest stack
> depth: 12088 bytes left
>
> netns_breakns 1 TBROK: unable to create veth pair devices
> Cannot find device \"veth0\"
>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
>
> Full test error log link,
> -------------------------
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.11.y/build/v5.11-13-g6380656c9227/testrun/4002283/suite/ltp-containers-tests/test/netns_breakns_ip_ipv4_ioctl/log
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v5.11-2899-g2c405d1ab8b3/testrun/3994442/suite/ltp-containers-tests/test/netns_breakns_ip_ipv4_ioctl/log
>
> --
> Linaro LKFT
> https://lkft.linaro.org
Thanks for the report. This has been fixed in -next and has a CC for
stable when it is merged into mainline:
https://git.kernel.org/next/linux-next/c/ebfac7b778fac8b0e8e92ec91d0b055f046b4604
https://github.com/ClangBuiltLinux/linux/issues/1250
Cheers,
Nathan
prev parent reply other threads:[~2021-02-22 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:31 clang-12: tun: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err -2) Naresh Kamboju
2021-02-22 19:37 ` 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=20210222193749.GA2954@24bbad8f3778 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox