From: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
To: andreyknvl@gmail.com
Cc: akpm@linux-foundation.org, bp@alien8.de, brauner@kernel.org,
dave.hansen@linux.intel.com, dhowells@redhat.com,
dvyukov@google.com, glider@google.com, hpa@zytor.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@redhat.com, ryabinin.a.a@gmail.com,
tglx@linutronix.de, vincenzo.frascino@arm.com, x86@kernel.org
Subject: Re: [PATCH v5] mm: x86: instrument __get/__put_kernel_nofault
Date: Fri, 27 Sep 2024 20:18:46 +0500 [thread overview]
Message-ID: <CACzwLxjpH=n5RDWnQCPZjH8i1GZAAbG-6BzuWCcVf99=qTO7HQ@mail.gmail.com> (raw)
In-Reply-To: <CACzwLxg7_HPxbjLT1v+dHG=V0wAcUJYZvqdcdLBD9xhLgNUmqQ@mail.gmail.com>
On Mon, Sep 23, 2024 at 11:09 AM Sabyrzhan Tasbolatov
<snovitoll@gmail.com> wrote:
>
> Instead of adding KASAN, KCSAN checks per arch macro,
> here is the alternative, generic way with a wrapper.
> I've tested it on x86_64 only, going to test on arm64
> with KASAN_SW_TAGS, KASAN_HW_TAGS if I can do it in qemu,
> and form a new patch for all arch
> and this PATCH v5 for x86 only can be abandoned.
>
> Please let me know if this wrapper is good enough,
> I will see in kasan_test.c how I should use SW/HW_TAG, probably,
> they should be a separate test with
> KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_SW_TAGS);
> ---
Hello,
I've sent a different patch [1] to support all arch checks,
tested on x86_64 and arm64 with SW/HW_TAGS.
This [PATCH v5] for the x86 only can be ignored.
[1] https://lore.kernel.org/linux-mm/20240927151438.2143936-1-snovitoll@gmail.com/T/#u
next prev parent reply other threads:[~2024-09-27 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 20:18 [PATCH] " Sabyrzhan Tasbolatov
2024-09-17 22:51 ` Andrey Konovalov
2024-09-18 10:56 ` [PATCH v2] " Sabyrzhan Tasbolatov
2024-09-18 15:15 ` Andrey Konovalov
2024-09-19 10:57 ` [PATCH v3] " Sabyrzhan Tasbolatov
2024-09-20 22:26 ` Andrey Konovalov
2024-09-21 7:10 ` [PATCH v4] " Sabyrzhan Tasbolatov
2024-09-21 20:49 ` Andrey Konovalov
2024-09-22 9:26 ` Sabyrzhan Tasbolatov
2024-09-22 12:04 ` Andrey Konovalov
2024-09-22 14:57 ` [PATCH v5] " Sabyrzhan Tasbolatov
2024-09-23 6:09 ` Sabyrzhan Tasbolatov
2024-09-27 15:18 ` Sabyrzhan Tasbolatov [this message]
2024-09-22 12:06 ` [PATCH v4] " Andrey Konovalov
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='CACzwLxjpH=n5RDWnQCPZjH8i1GZAAbG-6BzuWCcVf99=qTO7HQ@mail.gmail.com' \
--to=snovitoll@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=x86@kernel.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