From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Anton Altaparmakov <anton@tuxera.com>,
Joel Stanley <joel@jms.id.au>,
Michael Ellerman <mpe@ellerman.id.au>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build failure after merge of almost all the trees
Date: Tue, 2 Nov 2021 08:06:10 +0100 [thread overview]
Message-ID: <CAK8P3a3Fx0UmbxP48RnXHcJYf_tU3_NTkMZrFnM42eAb_F4jRQ@mail.gmail.com> (raw)
In-Reply-To: <20211102174400.1aaee22c@canb.auug.org.au>
On Tue, Nov 2, 2021 at 7:44 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> On Thu, 28 Oct 2021 23:38:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > On Thu, 28 Oct 2021 21:26:51 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Today's linux-next build (powerpc allyesconfig) failed like this:
> > >
> > > fs/ntfs/aops.c: In function 'ntfs_write_mst_block':
> > > fs/ntfs/aops.c:1311:1: error: the frame size of 2304 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
> > > 1311 | }
> > > | ^
> > > cc1: all warnings being treated as errors
> > >
> > > I have no idea what has caused this.
> >
> > With a nudge from Arnd, it seems the immediate case was commit
> >
> > f22969a66041 ("powerpc/64s: Default to 64K pages for 64 bit book3s")
> >
> > from the powerpc tree switching the allyesconfig build from 4k pages to
> > 64k pages which expanded a few arrays on the stack in that function.
>
> Can we do something about this, please?
I submitted a workaround a while ago. Anton didn't like it, but has not
come up with a proper fix in ntfs either:
https://lore.kernel.org/lkml/20210927141815.1711736-1-arnd@kernel.org/
It does need to be changed a bit as I realized it depends on a rework of
the Kconfig logic that I had in my randconfig build tree to have a common
page size symbol across architectures. Without my other patch, it also
needs to check for PPC_64K_PAGES.
Should I send an updated version of the patch?
Arnd
next prev parent reply other threads:[~2021-11-02 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 10:26 linux-next: build failure after merge of almost all the trees Stephen Rothwell
2021-10-28 12:38 ` Stephen Rothwell
2021-11-02 6:44 ` Stephen Rothwell
2021-11-02 7:06 ` Arnd Bergmann [this message]
2021-11-02 12:13 ` Stephen Rothwell
2021-11-02 12:19 ` Stephen Rothwell
2021-11-02 13:11 ` Arnd Bergmann
2021-11-03 4:47 ` Stephen Rothwell
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=CAK8P3a3Fx0UmbxP48RnXHcJYf_tU3_NTkMZrFnM42eAb_F4jRQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=anton@tuxera.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).