From: Marco Elver <elver@google.com>
To: Tianchen Ding <dtcccc@linux.alibaba.com>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] kfence: Allow re-enabling KFENCE after system startup
Date: Mon, 7 Mar 2022 15:08:03 +0100 [thread overview]
Message-ID: <CANpmjNNMQNd8LnCOaL0JXqS3r3Gv-DHrcw7Q6YvD6uWqnCz03Q@mail.gmail.com> (raw)
In-Reply-To: <20220307074516.6920-2-dtcccc@linux.alibaba.com>
On Mon, 7 Mar 2022 at 08:45, Tianchen Ding <dtcccc@linux.alibaba.com> wrote:
>
> If once KFENCE is disabled by:
> echo 0 > /sys/module/kfence/parameters/sample_interval
> KFENCE could never be re-enabled until next rebooting.
>
> Allow re-enabling it by writing a positive num to sample_interval.
>
> Signed-off-by: Tianchen Ding <dtcccc@linux.alibaba.com>
Reviewed-by: Marco Elver <elver@google.com>
> ---
> mm/kfence/core.c | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 13128fa13062..caa4e84c8b79 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -38,14 +38,17 @@
> #define KFENCE_WARN_ON(cond) \
> ({ \
> const bool __cond = WARN_ON(cond); \
> - if (unlikely(__cond)) \
> + if (unlikely(__cond)) { \
> WRITE_ONCE(kfence_enabled, false); \
> + disabled_by_warn = true; \
> + } \
> __cond; \
> })
>
> /* === Data ================================================================= */
>
> static bool kfence_enabled __read_mostly;
> +static bool disabled_by_warn __read_mostly;
>
> unsigned long kfence_sample_interval __read_mostly = CONFIG_KFENCE_SAMPLE_INTERVAL;
> EXPORT_SYMBOL_GPL(kfence_sample_interval); /* Export for test modules. */
> @@ -55,6 +58,7 @@ EXPORT_SYMBOL_GPL(kfence_sample_interval); /* Export for test modules. */
> #endif
> #define MODULE_PARAM_PREFIX "kfence."
>
> +static int kfence_enable_late(void);
> static int param_set_sample_interval(const char *val, const struct kernel_param *kp)
> {
> unsigned long num;
> @@ -65,10 +69,11 @@ static int param_set_sample_interval(const char *val, const struct kernel_param
>
> if (!num) /* Using 0 to indicate KFENCE is disabled. */
> WRITE_ONCE(kfence_enabled, false);
> - else if (!READ_ONCE(kfence_enabled) && system_state != SYSTEM_BOOTING)
> - return -EINVAL; /* Cannot (re-)enable KFENCE on-the-fly. */
>
> *((unsigned long *)kp->arg) = num;
> +
> + if (num && !READ_ONCE(kfence_enabled) && system_state != SYSTEM_BOOTING)
> + return disabled_by_warn ? -EINVAL : kfence_enable_late();
> return 0;
> }
>
> @@ -787,6 +792,16 @@ void __init kfence_init(void)
> (void *)(__kfence_pool + KFENCE_POOL_SIZE));
> }
>
> +static int kfence_enable_late(void)
> +{
> + if (!__kfence_pool)
> + return -EINVAL;
> +
> + WRITE_ONCE(kfence_enabled, true);
> + queue_delayed_work(system_unbound_wq, &kfence_timer, 0);
> + return 0;
> +}
> +
> void kfence_shutdown_cache(struct kmem_cache *s)
> {
> unsigned long flags;
> --
> 2.27.0
>
next prev parent reply other threads:[~2022-03-07 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 7:45 [PATCH v3 0/2] provide the flexibility to enable KFENCE Tianchen Ding
2022-03-07 7:45 ` [PATCH v3 1/2] kfence: Allow re-enabling KFENCE after system startup Tianchen Ding
2022-03-07 14:08 ` Marco Elver [this message]
2022-03-07 7:45 ` [PATCH v3 2/2] kfence: Alloc kfence_pool " Tianchen Ding
2022-03-07 14:08 ` Marco Elver
2022-03-10 1:43 ` liupeng (DM)
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=CANpmjNNMQNd8LnCOaL0JXqS3r3Gv-DHrcw7Q6YvD6uWqnCz03Q@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=dtcccc@linux.alibaba.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).