From: Marco Elver <elver@google.com>
To: Jackie Liu <liu.yun@linux.dev>
Cc: glider@google.com, dvyukov@google.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm/kfence: print disabling or re-enabling message
Date: Tue, 17 May 2022 13:42:03 +0200 [thread overview]
Message-ID: <YoOKC8oE7fbsWsyS@elver.google.com> (raw)
In-Reply-To: <20220517111551.4077061-1-liu.yun@linux.dev>
On Tue, May 17, 2022 at 07:15PM +0800, Jackie Liu wrote:
> From: Jackie Liu <liuyun01@kylinos.cn>
>
> By printing information, we can friendly prompt the status change
> information of kfence by dmesg.
>
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
Personally, I've never found this useful. If I want to get the current
accurate state of KFENCE enablement, I just look at
/sys/kernel/debug/kfence/stats.
Nevertheless, some comments below.
> ---
> mm/kfence/core.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 11a954763be9..beb552089b67 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -67,8 +67,11 @@ static int param_set_sample_interval(const char *val, const struct kernel_param
> if (ret < 0)
> return ret;
>
> - if (!num) /* Using 0 to indicate KFENCE is disabled. */
> + if (!num) {
> + /* Using 0 to indicate KFENCE is disabled. */
> WRITE_ONCE(kfence_enabled, false);
> + pr_info("KFENCE is disabled.\n");
This will also print on boot if kfence.sample_interval=0 is passed. This
is ugly.
We also have a pr_fmt, and writing "KFENCE" again is ugly, too. And
adding '.' at the end of these short log lines is not something done
much in the kernel, and also ugly.
So what you want is this fixup:
diff --git a/mm/kfence/core.c b/mm/kfence/core.c
index beb552089b67..de5bcf2609fe 100644
--- a/mm/kfence/core.c
+++ b/mm/kfence/core.c
@@ -67,10 +67,11 @@ static int param_set_sample_interval(const char *val, const struct kernel_param
if (ret < 0)
return ret;
+ /* Using 0 to indicate KFENCE is disabled. */
if (!num) {
- /* Using 0 to indicate KFENCE is disabled. */
+ if (READ_ONCE(kfence_enabled))
+ pr_info("disabled\n");
WRITE_ONCE(kfence_enabled, false);
- pr_info("KFENCE is disabled.\n");
}
*((unsigned long *)kp->arg) = num;
@@ -877,7 +878,7 @@ static int kfence_enable_late(void)
WRITE_ONCE(kfence_enabled, true);
queue_delayed_work(system_unbound_wq, &kfence_timer, 0);
- pr_info("KFENCE is re-enabled.\n");
+ pr_info("re-enabled\n");
return 0;
}
next prev parent reply other threads:[~2022-05-17 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 11:15 Jackie Liu
2022-05-17 11:42 ` Marco Elver [this message]
2022-05-18 0:39 ` Jackie Liu
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=YoOKC8oE7fbsWsyS@elver.google.com \
--to=elver@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=liu.yun@linux.dev \
/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