linux-kernel - Re: virt_to_phys outside array bounds warning (GCC 12.1.0)

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: <28ec9f61-3086-a12e-3e8d-33f855f916fc@gmail.com>
Date:   Wed, 8 Jun 2022 16:51:26 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Cc:     Benoît Cousson <bcousson@...libre.com>,
        Tony Lindgren <tony@...mide.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
        Russell King <linux@...linux.org.uk>,
        Linus Walleij <linus.walleij@...aro.org>,
        "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
        linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: virt_to_phys outside array bounds warning (GCC 12.1.0)

On 6/8/22 16:28, Krzysztof Kozlowski wrote:
> On 08/06/2022 10:39, Bagas Sanjaya wrote:
>> Hi everyone,
>>
>> When cross-compiling arm 5.19-rc1 kernel using GCC 12.1.0 (armv7 with neon
>> fpu, multi_v7_defconfig), I got outside array bounds warning pointing to
>> virt_to_phys() macro:
>>
> 
> Thanks for the report!
> 
> I think this was already reported:
> https://lore.kernel.org/all/CAK8P3a3X0UwQiVNZqvGmSKi8BX6zg=k07+9Q3rDGqHVkc8Hdsg@mail.gmail.com/
> 

The report above is for arm64, but similar to this report (arm report).

> Anyway, for the future:
> I don't think the CC list matches the problem. Please bisect this issue
> (since it is reproducible build time, it should be straightforward) to
> find offending commit and then Cc responsible people and maintainers
> (scripts/get_maintainer.pl). Ccing half-random people might not get
> necessary attention.
> 

I think the most likely culprit is commit 37efe6427dd50e ("[ARM] use asm/sections.h")
and 14c4a533e0996f ("ARM: 8583/1: mm: fix location of _etext").


Thanks.

-- 
An old man doll... just what I always wanted! - Clara