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 v3] mm/kfence: print disabling or re-enabling message
Date: Wed, 18 May 2022 09:24:57 +0200 [thread overview]
Message-ID: <CANpmjNMSnvKVYOwof1WSxVX+qRsKUK3QPjPuWk5KdNjwMkEfPQ@mail.gmail.com> (raw)
In-Reply-To: <20220518010319.4161482-1-liu.yun@linux.dev>
On Wed, 18 May 2022 at 03:03, Jackie Liu <liu.yun@linux.dev> wrote:
>
> From: Jackie Liu <liuyun01@kylinos.cn>
>
> By printing information, we can friendly prompt the status change
> information of kfence by dmesg and record by syslog.
>
> Co-developed-by: Marco Elver <elver@google.com>
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
> ---
> v1->v2:
> fixup by Marco Elver <elver@google.com>
> v2->v3:
> write kfence_enabled=false only true before
>
> mm/kfence/core.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 11a954763be9..41840b8d9cb3 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -67,8 +67,13 @@ 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. */
> - WRITE_ONCE(kfence_enabled, false);
> + /* Using 0 to indicate KFENCE is disabled. */
> + if (!num) {
> + if (READ_ONCE(kfence_enabled)) {
Now you could just write
if (!num && READ_ONCE(kfence_enabled)) {
....
> + pr_info("disabled\n");
> + WRITE_ONCE(kfence_enabled, false);
> + }
> + }
>
> *((unsigned long *)kp->arg) = num;
>
> @@ -874,6 +879,7 @@ static int kfence_enable_late(void)
>
> WRITE_ONCE(kfence_enabled, true);
> queue_delayed_work(system_unbound_wq, &kfence_timer, 0);
> + pr_info("re-enabled\n");
> return 0;
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-05-18 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 1:03 Jackie Liu
2022-05-18 7:24 ` Marco Elver [this message]
2022-05-18 7:26 ` 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=CANpmjNMSnvKVYOwof1WSxVX+qRsKUK3QPjPuWk5KdNjwMkEfPQ@mail.gmail.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