linux-kernel - Re: clang-17: selftests: sgx: clang: error: -z noexecstack: 'linker' input unused [-Werror,-Wunused-command-line-argument]

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] [day] [month] [year] [list]

Message-ID: <CAKwvOdmMYzDNK0+un0xossc4f7-A3=EZo11VnVx5Bf0THWhhpw@mail.gmail.com>
Date:   Mon, 21 Aug 2023 11:15:28 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     clang-built-linux <llvm@...ts.linux.dev>,
        open list <linux-kernel@...r.kernel.org>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>, lkft-triage@...ts.linaro.org,
        Nathan Chancellor <nathan@...nel.org>,
        Shuah Khan <shuah@...nel.org>,
        Anders Roxell <anders.roxell@...aro.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: clang-17: selftests: sgx: clang: error: -z noexecstack: 'linker'
 input unused [-Werror,-Wunused-command-line-argument]

On Mon, Aug 21, 2023 at 6:52 AM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> Recently we have updated the toolchain clang-17 version.
>
> While building selftests sgx following warnings / errors noticed on the
> Linux next with clang-17.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> sgx/main.o
> clang: error: -z noexecstack: 'linker' input unused
> [-Werror,-Wunused-command-line-argument]

Hi Naresh,
Thanks for the report.

I think in general for the kselftests, these aren't really
regressions; we've simply not spent the time to sit down and get them
all building.

That said, we should.

Since this isn't a recent regression, would you mind instead of
emailing the list instead file an individual issue at our issue
tracker per diagnostic identified?

https://github.com/ClangBuiltLinux/linux/issues

We are very active in tracking the progress on issues there. I would
love for you and the LKFT team to participate with us there.

https://github.com/ClangBuiltLinux/linux/issues/1698 is the meta issue
tracking the kselftest targets.

When we have a target building that regresses, then we should notify
the list, but until then I think it may be less noisy to get issues on
file.

>
> Links:
>  - https://storage.tuxsuite.com/public/linaro/lkft/builds/2UHhSg0TPLhjp9Uq9EFceoQd0VL/
>
> Steps to reproduce:
>  - https://storage.tuxsuite.com/public/linaro/lkft/builds/2UHhSg0TPLhjp9Uq9EFceoQd0VL/tuxmake_reproducer.sh
>
> tuxmake --runtime podman --target-arch x86_64 --toolchain clang-17
> --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2UHhSg0TPLhjp9Uq9EFceoQd0VL/config
> LLVM=1 LLVM_IAS=1 debugkernel cpupower headers kernel kselftest
> modules

Any chance you can extract the invocation of `make` from the above for
the bug reports?  I'm guessing

`make LLVM=1 debugkernel cpupower headers kernel kselftest`?
(LLVM_IAS=1 should be obsolete on mainline)

>
>
> --
> Linaro LKFT
> https://lkft.linaro.org

-- 
Thanks,
~Nick Desaulniers