From: Andrey Konovalov <andreyknvl@gmail.com>
To: Marco Elver <elver@google.com>
Cc: andrey.konovalov@linux.dev,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
kasan-dev@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH 3/5] kasan: use unchecked __memset internally
Date: Mon, 9 Oct 2023 21:50:06 +0200 [thread overview]
Message-ID: <CA+fCnZc+JVdxzfiaSon+0V6-5c7SsXv8pNUvjWsfiLPyvMr9Ow@mail.gmail.com> (raw)
In-Reply-To: <CANpmjNOHPRHOOPNwx04S_CE5OoQMAmfxHjxqeqy=YUpU+sY7yA@mail.gmail.com>
On Mon, Oct 9, 2023 at 10:46 AM Marco Elver <elver@google.com> wrote:
>
> On Fri, 6 Oct 2023 at 17:18, <andrey.konovalov@linux.dev> wrote:
> >
> > From: Andrey Konovalov <andreyknvl@google.com>
> >
> > KASAN code is supposed to use the unchecked __memset implementation when
> > accessing its metadata.
> >
> > Change uses of memset to __memset in mm/kasan/.
> >
> > Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
>
> Do we need a "Fixes" tag?
Good idea, let's add them:
Fixes: 59e6e098d1c1 ("kasan: introduce kasan_complete_mode_report_info")
Fixes: 3c5c3cfb9ef4 ("kasan: support backing vmalloc space with real
shadow memory")
> Reviewed-by: Marco Elver <elver@google.com>
Thanks!
next prev parent reply other threads:[~2023-10-09 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:18 [PATCH 0/5] kasan: assorted fixes and improvements andrey.konovalov
2023-10-06 15:18 ` [PATCH 1/5] arm64, kasan: update comment in kasan_init andrey.konovalov
2023-10-06 15:18 ` [PATCH 2/5] kasan: unify printk prefixes andrey.konovalov
2023-10-09 8:43 ` Marco Elver
2023-10-06 15:18 ` [PATCH 3/5] kasan: use unchecked __memset internally andrey.konovalov
2023-10-09 8:45 ` Marco Elver
2023-10-09 19:50 ` Andrey Konovalov [this message]
2023-10-06 15:18 ` [PATCH 4/5] kasan: fix and update KUNIT_EXPECT_KASAN_FAIL comment andrey.konovalov
2023-10-09 8:47 ` Marco Elver
2023-10-09 19:42 ` Andrey Konovalov
2023-10-06 15:18 ` [PATCH 5/5] Documentation: *san: drop "the" from article titles andrey.konovalov
2023-10-07 7:01 ` Marco Elver
2023-10-09 19:44 ` 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=CA+fCnZc+JVdxzfiaSon+0V6-5c7SsXv8pNUvjWsfiLPyvMr9Ow@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@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