public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Tiffany Yang <ynaffit@google.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: Fri, 5 Dec 2025 09:05:46 +0000	[thread overview]
Message-ID: <20251205090546.69158d85@pumpkin> (raw)
In-Reply-To: <530c975d-7fee-f6bb-948c-53c6af4a91be@nerdbynature.de>

On Fri, 5 Dec 2025 01:49:00 +0100 (CET)
Christian Kujau <lists@nerdbynature.de> wrote:

> Hi Tiffany,
> 
> On Tue, 25 Nov 2025, Tiffany Yang wrote:
> > 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  
> 
> Sorry for the late response. And thanks for resurrecting!
> 
> > 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,  
> 
> Interesting. I really did "allnoconfig" and then turned on a few debug 
> options via "menuconfig", I did not set CONFIG_STACK_WARN manually. Thanks 
> for spotting this, I'll look into my cross-build routine if something 
> funny happens there.
> 
> > 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!  
> 
> Yes, a proper fix would be great too.

Can't remember if I mentioned it before, but I suspect that letting
mas_commit_b_node() be inlined and then stopping both mas_rebalance()
and mas_split() being inlined into it (both of which are big and slow)
for all builds (not just KASAN ones) will reduce the overall stack slightly.

	David


> 
> cheers,
> Christian.


      reply	other threads:[~2025-12-05  9:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 13:35 maple_tree.c:3738:1: error: the frame size of 1040 bytes is larger than 1024 bytes 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
2025-12-05  0:49           ` Christian Kujau
2025-12-05  9:05             ` David Laight [this message]

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=20251205090546.69158d85@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=ynaffit@google.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