From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Chris Li <chrisl@kernel.org>, linux-mm <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Kairui Song <kasong@tencent.com>, Barry Song <21cnbao@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>,
Hugh Dickins <hughd@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: gcc-8: mm/swapfile.c:863:40: error: array subscript 1 is above array bounds of 'struct list_head[1]' [-Werror=array-bounds]
Date: Mon, 19 Aug 2024 15:45:47 +0530 [thread overview]
Message-ID: <CA+G9fYtd1Hw9YLpceUAwwC+UytVQVXOET4gmGT9jiCgHa+WexQ@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYuFDon59=Nw6WCdgp0FanZ1oE3dCkoq71EK0Bxe6Jhe_g@mail.gmail.com>
On Mon, 19 Aug 2024 at 13:58, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> The x86 builds failed with gcc-8 due to following build warnings / errors on
> Linux next-20240802 to next-20240819.
>
> x86_64 defconfig gcc-8 build failed
> x86_64 defconfig gcc-13 build pass
>
> First seen on the next-20240802 tag.
>
> GOOD: next-20240730
> BAD: next-20240802
Anders bisected this and found the first bad commit id as,
aded4352f648 ("mm: swap: separate SSD allocation from
scan_swap_map_slots()") first faulty one
- Naresh
next prev parent reply other threads:[~2024-08-19 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 8:28 Naresh Kamboju
2024-08-19 10:15 ` Naresh Kamboju [this message]
2024-08-19 11:44 ` Kairui Song
2024-08-19 19:57 ` Naresh Kamboju
2024-08-20 5:05 ` Andrew Morton
2024-08-20 8:51 ` Chris Li
2024-08-27 8:47 ` Kairui Song
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=CA+G9fYtd1Hw9YLpceUAwwC+UytVQVXOET4gmGT9jiCgHa+WexQ@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=chrisl@kernel.org \
--cc=hughd@google.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox