From: Wei Yang <richard.weiyang@gmail.com>
To: Scall <scall@prosemail.net>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: Re: lib/maple_tree.c:4056:1: error: the frame size of 1144 bytes is larger than 1024 bytes
Date: Fri, 31 Jan 2025 12:28:01 +0000 [thread overview]
Message-ID: <20250131122801.rb3bid7peznbgxwg@master> (raw)
In-Reply-To: <8415a24a-a19e-46f6-bb56-dfd529143dd9@prosemail.net>
Hi, Scall
On Thu, Jan 30, 2025 at 11:31:50PM +0100, Scall wrote:
>On 1/30/25 5:13 PM, Liam R. Howlett wrote:
>> Do you have KASAN or lock debugging on?
>
>No, I don't.
>
>> Does the issue go away when reverting 8c7904a8cd0df ("maple_tree: i is
>> always less than or equal to mas_end") ?
>
>That commit has not been backported to the kernel version I tried to build
>(6.12.11, currently the latest stable version).
Is there a public git tree to get the code you do build?
>
>Good news: I learned that the issue has already been solved in the mainline
>version with commit 5059aa6334fcf ("maple_tree: memset maple_big_node as a
>whole") and backporting it is the solution.
Or, is it possible to list the last several commits of file lib/maple_tree.c
so that I can reproduce it on my side.
I guess maybe I can try to reproduce this with:
* set CONFIG_FRAM_WARN to 1024
* set KCFLAGS="-O3"
I would try to take a look first.
Is the GCC version matters? I don't have the exact version at hand. Have you
tried other version?
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-01-31 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60cee319-4914-4a98-b74d-32e06fb3cbd8@prosemail.net>
2025-01-30 16:13 ` Liam R. Howlett
[not found] ` <8415a24a-a19e-46f6-bb56-dfd529143dd9@prosemail.net>
2025-01-31 12:28 ` Wei Yang [this message]
2025-01-31 13:37 ` Wei Yang
2025-01-31 15:08 ` Liam R. Howlett
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=20250131122801.rb3bid7peznbgxwg@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=scall@prosemail.net \
/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