linux-kernel - Re: landlock: fs_test: fs_test.c:4524:9: error: initializer element is not a compile-time constant

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]

Date:   Fri, 18 Aug 2023 10:48:41 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
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>, linux-fsdevel@...r.kernel.org,
        lkft-triage@...ts.linaro.org, Shuah Khan <shuah@...nel.org>,
        Anders Roxell <anders.roxell@...aro.org>,
        Mickaël Salaün <mic@...ikod.net>,
        Richard Weinberger <richard@....at>
Subject: Re: landlock: fs_test: fs_test.c:4524:9: error: initializer element
 is not a compile-time constant

On Thu, 17 Aug 2023 at 21:24, Nick Desaulniers <ndesaulniers@...gle.com> wrote:
>
> On Thu, Aug 17, 2023 at 3:51 AM Naresh Kamboju
> <naresh.kamboju@...aro.org> wrote:
> >
> > While building selftests landlock following warnings / errors noticed on the
> > Linux next with clang-17.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> >
> > Build errors:
> > ------------
> > landlock/fs_test
> > fs_test.c:4524:9: error: initializer element is not a compile-time constant
>
> Hi Naresh,
> Can you tell me more about your specific version of clang-17?

    compiler:
        name: clang,
        version: 17.0.0,
        version_full: Debian clang version 17.0.0
(++20230725053429+d0b54bb50e51-1~exp1~20230725173444.1)

>
> I believe a fix of mine to clang should address this. It landed in
> clang-18, and was backported to clang-17 recently.
> https://github.com/llvm/llvm-project-release-prs/commit/0b2d5b967d98375793897295d651f58f6fbd3034
>
> I suspect your clang-17 might need a rebuild.  Thanks for the report.

I will rebuild / re-test and confirm soon.

- Naresh