mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tiffany Yang <ynaffit@google.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: David Laight <david.laight.linux@gmail.com>,
	linux-kernel@vger.kernel.org,
	 "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: maple_tree.c:3738:1: error: the frame size of 1040 bytes is larger than 1024 bytes
Date: Tue, 25 Nov 2025 15:09:48 -0800	[thread overview]
Message-ID: <dbx8wm3dogjn.fsf@ynaffit-andsys.c.googlers.com> (raw)
In-Reply-To: <aee90be9-4816-592e-632b-21cbea4bb3dd@nerdbynature.de> (Christian Kujau's message of "Thu, 30 Oct 2025 18:13:33 +0100 (CET)")

Hi Christian,

Sorry to resurrect this old thread, but I wanted to reply in case you
were still thinking about this for whatever reason. I was running into a
similar issue with building UML, and then I found Geert's reply [1] in a
related thread.

Christian Kujau <lists@nerdbynature.de> writes:

> On Thu, 30 Oct 2025, David Laight wrote:
>> It is horrendous - best part of 4k code, the stack frame is 0x408.
>> Which means I must be building with a larger stack frame limit.
>> Is one of your debug options reducing it?

> No that I know of. I've attached the config to my initial posting.


I'm not sure how you set your config initially, but what jumps out at me
is that CONFIG_STACK_WARN=1024 even though
CONFIG_64BIT=y. CONFIG_STACK_WARN defaults to 2048 for 64-bit builds,
which is why other people don't seem to be running into this issue (at
least from glancing over the mailing list).

Obviously, this doesn't solve the actual problem, but from Liam's reply
further up in the thread, it looks like he's working on a fix, so now
you can keep your eye out for that!

[1]  
https://lore.kernel.org/all/CAMuHMdVqOR2kPy7V+N5oCFrKZA0R7JHC_+QsjFc5c43F1KFFiw@mail.gmail.com/

-- 
Tiffany Y. Yang

  parent reply	other threads:[~2025-11-25 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 13:35 Christian Kujau
2025-10-30 14:34 ` David Laight
2025-10-30 14:48   ` Christian Kujau
2025-10-30 16:51     ` David Laight
2025-10-30 17:13       ` Christian Kujau
2025-10-30 17:25         ` Christian Kujau
2025-10-30 20:56         ` David Laight
2025-11-25 23:09         ` Tiffany Yang [this message]
2025-12-05  0:49           ` Christian Kujau
2025-12-05  9:05             ` David Laight

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=dbx8wm3dogjn.fsf@ynaffit-andsys.c.googlers.com \
    --to=ynaffit@google.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=arnd@arndb.de \
    --cc=david.laight.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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

all inboxes | Powered by JetHome®