All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	"Russell King" <linux@armlinux.org.uk>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
	"Naresh Kamboju" <naresh.kamboju@linaro.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: virt_to_phys outside array bounds warning (GCC 12.1.0)
Date: Wed, 8 Jun 2022 16:51:26 +0700	[thread overview]
Message-ID: <28ec9f61-3086-a12e-3e8d-33f855f916fc@gmail.com> (raw)
In-Reply-To: <e8f8f42b-9df3-d9a1-893e-0f972e27ef80@linaro.org>

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	"Russell King" <linux@armlinux.org.uk>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, "Kees Cook" <keescook@chromium.org>,
	"Naresh Kamboju" <naresh.kamboju@linaro.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: virt_to_phys outside array bounds warning (GCC 12.1.0)
Date: Wed, 8 Jun 2022 16:51:26 +0700	[thread overview]
Message-ID: <28ec9f61-3086-a12e-3e8d-33f855f916fc@gmail.com> (raw)
In-Reply-To: <e8f8f42b-9df3-d9a1-893e-0f972e27ef80@linaro.org>

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

  reply	other threads:[~2022-06-08  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  8:39 virt_to_phys outside array bounds warning (GCC 12.1.0) Bagas Sanjaya
2022-06-08  8:39 ` Bagas Sanjaya
2022-06-08  9:28 ` Krzysztof Kozlowski
2022-06-08  9:28   ` Krzysztof Kozlowski
2022-06-08  9:51   ` Bagas Sanjaya [this message]
2022-06-08  9:51     ` Bagas Sanjaya

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=28ec9f61-3086-a12e-3e8d-33f855f916fc@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=keescook@chromium.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=naresh.kamboju@linaro.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.