From: Marco Elver <elver@google.com>
To: andrey.konovalov@linux.dev
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH mm] kasan: fix for "kasan: rename and document kasan_(un)poison_object_data"
Date: Thu, 21 Dec 2023 21:06:29 +0100 [thread overview]
Message-ID: <CANpmjNNY81MMtRVgux5725viFoq2i7PzjVvrnbJmT8ArmTMBUA@mail.gmail.com> (raw)
In-Reply-To: <20231221180637.105098-1-andrey.konovalov@linux.dev>
On Thu, 21 Dec 2023 at 19:06, <andrey.konovalov@linux.dev> wrote:
>
> From: Andrey Konovalov <andreyknvl@google.com>
>
> Update references to renamed functions in comments.
>
> Fixes: ac6b240e1ede ("kasan: rename and document kasan_(un)poison_object_data")
> Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Reviewed-by: Marco Elver <elver@google.com>
> ---
> mm/kasan/shadow.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/kasan/shadow.c b/mm/kasan/shadow.c
> index d687f09a7ae3..0154d200be40 100644
> --- a/mm/kasan/shadow.c
> +++ b/mm/kasan/shadow.c
> @@ -130,7 +130,7 @@ void kasan_poison(const void *addr, size_t size, u8 value, bool init)
>
> /*
> * Perform shadow offset calculation based on untagged address, as
> - * some of the callers (e.g. kasan_poison_object_data) pass tagged
> + * some of the callers (e.g. kasan_poison_new_object) pass tagged
> * addresses to this function.
> */
> addr = kasan_reset_tag(addr);
> @@ -170,7 +170,7 @@ void kasan_unpoison(const void *addr, size_t size, bool init)
>
> /*
> * Perform shadow offset calculation based on untagged address, as
> - * some of the callers (e.g. kasan_unpoison_object_data) pass tagged
> + * some of the callers (e.g. kasan_unpoison_new_object) pass tagged
> * addresses to this function.
> */
> addr = kasan_reset_tag(addr);
> --
> 2.25.1
>
prev parent reply other threads:[~2023-12-21 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 18:06 andrey.konovalov
2023-12-21 20:06 ` 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=CANpmjNNY81MMtRVgux5725viFoq2i7PzjVvrnbJmT8ArmTMBUA@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=andreyknvl@gmail.com \
--cc=andreyknvl@google.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=ryabinin.a.a@gmail.com \
/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