From: "Arnd Bergmann" <arnd@kernel.org>
To: "Peng Fan" <peng.fan@nxp.com>,
"Kent Overstreet" <kent.overstreet@linux.dev>
Cc: "linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: error: the frame size of 1552 bytes is larger than 1280 bytes when building bcachefs
Date: Thu, 22 May 2025 13:23:56 +0200 [thread overview]
Message-ID: <d8e9f098-49a2-4f1e-a6a5-7a6437658d93@app.fastmail.com> (raw)
In-Reply-To: <PAXPR04MB845954FBBF2AD810B17536138899A@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Thu, May 22, 2025, at 08:39, Peng Fan wrote:
> Hi Kent, Arnd
>
> There is below build error with "make ARCH=arm randconfig; make"
>
> fs/bcachefs/data_update.c: In function
> '__bch2_data_update_index_update':
> fs/bcachefs/data_update.c:439:1: error: the frame size of 1552 bytes is
> larger than 1280 bytes [-Werror=frame-larger-than=]
Right, I think that's been the case with bcachefs since the start,
and I see it with allmodconfig as well, the problem being mostly
CONFIG_KASAN_STACK.
There are a couple of bcachefs functions that have an unusual number
of local struct variables in them, and KASAN_STACK adds a redzone
around each one of them, further increasing the size.
When I add "depends on !KASAN_STACK" to bcachefs, I see all
randconfig builds succeeding, but that may not be the best
solution.
Arnd
next prev parent reply other threads:[~2025-05-22 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:39 error: the frame size of 1552 bytes is larger than 1280 bytes when building bcachefs Peng Fan
2025-05-22 11:23 ` Arnd Bergmann [this message]
2025-05-22 11:29 ` Kent Overstreet
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=d8e9f098-49a2-4f1e-a6a5-7a6437658d93@app.fastmail.com \
--to=arnd@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=peng.fan@nxp.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