From: Andrew Morton <akpm@linux-foundation.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "SeongJae Park" <sj@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Ravi Jonnalagadda" <ravis.opensrc@gmail.com>,
"Quanmin Yan" <yanquanmin1@huawei.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] mm/damon/core: reduce kernel stack usage
Date: Tue, 30 Jun 2026 13:45:40 -0700 [thread overview]
Message-ID: <20260630134540.550e55ba610ea956111d1e6f@linux-foundation.org> (raw)
In-Reply-To: <0c57d639-259c-4498-9b7f-3ac46d669935@app.fastmail.com>
On Tue, 30 Jun 2026 15:29:03 +0200 "Arnd Bergmann" <arnd@arndb.de> wrote:
> This is clearly an
> uphill battle, but kernel stack overflows are a real and build testing
> with a reasonably small limit is only one line of defense against these.
It's a worthy battle.
Reducing the default CONFIG_FRAME_WARN on various architectures will
help. It's kinda trollish, but we should clamp down on this stuff and
having Arnd plugging away on his own isn't a good way!
next prev parent reply other threads:[~2026-06-30 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 12:56 [PATCH] mm/damon/core: reduce kernel stack usage Arnd Bergmann
2026-06-11 13:56 ` SeongJae Park
2026-06-28 5:34 ` Andrew Morton
2026-06-28 16:50 ` SJ Park
2026-06-30 13:29 ` Arnd Bergmann
2026-06-30 20:45 ` Andrew Morton [this message]
2026-06-11 18:50 ` David Laight
2026-06-12 17:08 ` Arnd Bergmann
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=20260630134540.550e55ba610ea956111d1e6f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=damon@lists.linux.dev \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ravis.opensrc@gmail.com \
--cc=sj@kernel.org \
--cc=yanquanmin1@huawei.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