From: Marco Elver <elver@google.com>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/kfence: Use str_write_read() helper in get_access_type()
Date: Wed, 15 Jan 2025 10:47:35 +0100 [thread overview]
Message-ID: <CANpmjNOO3TgBg+LACvWH0+6W0+N1eUmDsoQUt0MT3X+UubBSgA@mail.gmail.com> (raw)
In-Reply-To: <20250115090303.918192-2-thorsten.blum@linux.dev>
On Wed, 15 Jan 2025 at 10:03, Thorsten Blum <thorsten.blum@linux.dev> wrote:
>
> Remove hard-coded strings by using the str_write_read() helper function.
>
> Suggested-by: Anshuman Khandual <anshuman.khandual@arm.com>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> mm/kfence/kfence_test.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Why only change the one in kfence_test.c?
$ grep '"read"' mm/kfence/*
mm/kfence/kfence_test.c: return r->is_write ? "write" : "read";
mm/kfence/report.c: return is_write ? "write" : "read";
> diff --git a/mm/kfence/kfence_test.c b/mm/kfence/kfence_test.c
> index f65fb182466d..00034e37bc9f 100644
> --- a/mm/kfence/kfence_test.c
> +++ b/mm/kfence/kfence_test.c
> @@ -20,6 +20,7 @@
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> #include <linux/string.h>
> +#include <linux/string_choices.h>
> #include <linux/tracepoint.h>
> #include <trace/events/printk.h>
>
> @@ -88,7 +89,7 @@ struct expect_report {
>
> static const char *get_access_type(const struct expect_report *r)
> {
> - return r->is_write ? "write" : "read";
> + return str_write_read(r->is_write);
> }
>
> /* Check observed report matches information in @r. */
> --
> 2.47.1
>
> --
> You received this message because you are subscribed to the Google Groups "kasan-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kasan-dev+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/kasan-dev/20250115090303.918192-2-thorsten.blum%40linux.dev.
prev parent reply other threads:[~2025-01-15 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:03 Thorsten Blum
2025-01-15 9:47 ` Marco Elver [this message]
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=CANpmjNOO3TgBg+LACvWH0+6W0+N1eUmDsoQUt0MT3X+UubBSgA@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.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 \
--cc=thorsten.blum@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