From: SeongJae Park <sj@kernel.org>
To: flyingpenghao@gmail.com
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, Peng Hao <flyingpeng@tencent.com>
Subject: Re: [PATCH v5] mm/damon/lru_sort: adjust local variable to dynamic allocation
Date: Tue, 23 Jul 2024 09:08:43 -0700 [thread overview]
Message-ID: <20240723160843.99979-1-sj@kernel.org> (raw)
In-Reply-To: <20240723035513.20153-1-flyingpeng@tencent.com>
Hi Peng,
Thank you for patiently following the discussion and sending this, Peng!
On Tue, 23 Jul 2024 11:55:13 +0800 flyingpenghao@gmail.com wrote:
> From: Peng Hao <flyingpeng@tencent.com>
>
> When KASAN is enabled and built with clang:
> mm/damon/lru_sort.c:199:12: error: stack frame size (2328) exceeds
> limit (2048) in 'damon_lru_sort_apply_parameters' [-Werror,-Wframe-larger-than]
> static int damon_lru_sort_apply_parameters(void)
> ^
> 1 error generated.
>
> This is because damon_lru_sort_quota contains a large array, and
> assigning this variable to a local variable causes a large amount of
> stack space to be occupied.
>
> So adjust local variable to dynamic allocation.
>
> Link: https://lore.kernel.org/all/20240711081051.66560-1-flyingpeng@tencent.com/
> Link: https://lore.kernel.org/linux-mm/20240719174234.47017-1-sj@kernel.org/T/
I guess above two links are for revision history of this patch? If so, it
would better to put together with revision history under the below '---' line.
If not, it would be better to add more clear contexts on the commit message.
>
> Signed-off-by: Peng Hao <flyingpeng@tencent.com>
Except the above trivial comment,
Reviewed-by: SeongJae Park <sj@kernel.org>
I think Andrew would handle the trivial comment on his own when he add this
patch to mm tree. You could post v6 with the above my Reviewed-by: tag if you
prefer to, of course.
Thanks,
SJ
[...]
prev parent reply other threads:[~2024-07-23 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 3:55 flyingpenghao
2024-07-23 16:08 ` SeongJae Park [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=20240723160843.99979-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=flyingpeng@tencent.com \
--cc=flyingpenghao@gmail.com \
--cc=linux-mm@kvack.org \
/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