From: Andrew Morton <akpm@linux-foundation.org>
To: yuan linyu <yuanlinyu@honor.com>
Cc: Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>, <kasan-dev@googlegroups.com>,
<linux-mm@kvack.org>, <loongarch@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] kfence: allow change number of object by early parameter
Date: Thu, 18 Dec 2025 15:58:21 -0800 [thread overview]
Message-ID: <20251218155821.92454cbb7117c27c1b914ce0@linux-foundation.org> (raw)
In-Reply-To: <20251218015849.1414609-4-yuanlinyu@honor.com>
On Thu, 18 Dec 2025 09:58:49 +0800 yuan linyu <yuanlinyu@honor.com> wrote:
> when want to change the kfence pool size, currently it is not easy and
> need to compile kernel.
>
> Add an early boot parameter kfence.num_objects to allow change kfence
> objects number and allow increate total pool to provide high failure
> rate.
>
> ...
>
> include/linux/kfence.h | 5 +-
> mm/kfence/core.c | 122 +++++++++++++++++++++++++++++-----------
> mm/kfence/kfence.h | 4 +-
> mm/kfence/kfence_test.c | 2 +-
Can you please add some documentation in Documentation/dev-tools/kfence.rst?
Also, this should be described in
Documentation/admin-guide/kernel-parameters.txt. That file doesn't
mention kfence at all, which might be an oversight.
Meanwhile, I'll queue these patches in mm.git's mm-nonmm-unstable
branch for some testing. I'll await reviewer input before proceeding
further. Thanks.
next prev parent reply other threads:[~2025-12-18 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 1:58 [PATCH 0/3] kfence: allow change objects number yuan linyu
2025-12-18 1:58 ` [PATCH 1/3] LoongArch: kfence: avoid use CONFIG_KFENCE_NUM_OBJECTS yuan linyu
2025-12-18 1:58 ` [PATCH 2/3] kfence: allow create debugfs dir/file unconditionally yuan linyu
2025-12-18 1:58 ` [PATCH 3/3] kfence: allow change number of object by early parameter yuan linyu
2025-12-18 23:58 ` Andrew Morton [this message]
2025-12-19 0:03 ` Marco Elver
2025-12-19 0:08 ` Andrew Morton
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=20251218155821.92454cbb7117c27c1b914ce0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=loongarch@lists.linux.dev \
--cc=yuanlinyu@honor.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