linux-kernel - Re: lib/test_bitmap.c:920:2: error: call to __compiletime_assert_372 declared with 'error' attribute: BUILD_BUG_ON failed: !__builtin_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] [day] [month] [year] [list]

Message-ID: <ZJmR6zrjDZgDvWCA@smile.fi.intel.com>
Date:   Mon, 26 Jun 2023 16:26:03 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Alexander Lobakin <aleksander.lobakin@...el.com>
Cc:     Nick Desaulniers <ndesaulniers@...gle.com>,
        kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
        oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
        Yury Norov <yury.norov@...il.com>
Subject: Re: lib/test_bitmap.c:920:2: error: call to __compiletime_assert_372
 declared with 'error' attribute: BUILD_BUG_ON failed:
 !__builtin_constant_p(res)

On Mon, Jun 26, 2023 at 01:57:46PM +0200, Alexander Lobakin wrote:
> From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> Date: Mon, 26 Jun 2023 11:32:51 +0300
> > On Sun, Jun 25, 2023 at 05:12:36AM +0800, kernel test robot wrote:
> >> Hi Alexander,
> >>
> >> FYI, the error/warning still remains.
> > 
> > Alexander, do you have anything to present to fix this? Or is your plan to send
> > something after v6.5-rc1?
> 
> I was waiting for an email from Nick (or some further update of the
> GitHub issue page) to clarify whether the compiler should be fixed or I
> should work around this in the code.

Okay, got it! Maybe you can ping him?

> If the latter, I could send a fix
> this week, so that it could even hit the bitmap pull request.

It could hit a PR after v6.5-rc1 (Linus expects the following: a) the PR
to be send in the _first_ week of merge window with rare exceptions, and
b) the commits in PR has to be sit in Linux Next for a while, usually
a couple of weeks).

-- 
With Best Regards,
Andy Shevchenko