* [PATCH] mm/kfence: Use str_write_read() helper in get_access_type()
@ 2025-01-15 9:03 Thorsten Blum
2025-01-15 9:47 ` Marco Elver
0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Blum @ 2025-01-15 9:03 UTC (permalink / raw)
To: Alexander Potapenko, Marco Elver, Dmitry Vyukov, Andrew Morton
Cc: Thorsten Blum, Anshuman Khandual, kasan-dev, linux-mm, linux-kernel
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(-)
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] mm/kfence: Use str_write_read() helper in get_access_type()
2025-01-15 9:03 [PATCH] mm/kfence: Use str_write_read() helper in get_access_type() Thorsten Blum
@ 2025-01-15 9:47 ` Marco Elver
0 siblings, 0 replies; 2+ messages in thread
From: Marco Elver @ 2025-01-15 9:47 UTC (permalink / raw)
To: Thorsten Blum
Cc: Alexander Potapenko, Dmitry Vyukov, Andrew Morton,
Anshuman Khandual, kasan-dev, linux-mm, linux-kernel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-01-15 9:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-15 9:03 [PATCH] mm/kfence: Use str_write_read() helper in get_access_type() Thorsten Blum
2025-01-15 9:47 ` Marco Elver
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox