From: Alexander Potapenko <glider@google.com>
To: Kees Cook <keescook@chromium.org>
Cc: andy@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
nathan@kernel.org, dvyukov@google.com, elver@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, ndesaulniers@google.com
Subject: Re: [PATCH v2] string: use __builtin_memcpy() in strlcpy/strlcat
Date: Wed, 31 May 2023 09:57:57 +0200 [thread overview]
Message-ID: <CAG_fn=VOsPw=EqN=P3zPfDyD=ZKYtzUVZ=y42HcqrY2hznx6Ug@mail.gmail.com> (raw)
In-Reply-To: <168548824525.1351231.6995242566921339574.b4-ty@chromium.org>
On Wed, May 31, 2023 at 1:10 AM Kees Cook <keescook@chromium.org> wrote:
>
> On Tue, 30 May 2023 10:39:11 +0200, Alexander Potapenko wrote:
> > lib/string.c is built with -ffreestanding, which prevents the compiler
> > from replacing certain functions with calls to their library versions.
> >
> > On the other hand, this also prevents Clang and GCC from instrumenting
> > calls to memcpy() when building with KASAN, KCSAN or KMSAN:
> > - KASAN normally replaces memcpy() with __asan_memcpy() with the
> > additional cc-param,asan-kernel-mem-intrinsic-prefix=1;
> > - KCSAN and KMSAN replace memcpy() with __tsan_memcpy() and
> > __msan_memcpy() by default.
> >
> > [...]
>
> Applied to for-next/hardening, thanks!
>
> [1/1] string: use __builtin_memcpy() in strlcpy/strlcat
> https://git.kernel.org/kees/c/cfe93c8c9a7a
Note that Andrew also picked it to mm-unstable
prev parent reply other threads:[~2023-05-31 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:39 [PATCH v2] string: use __builtin_memcpy() in strlcpy/strlcat Alexander Potapenko
2023-05-30 8:40 ` Alexander Potapenko
2023-05-30 23:10 ` Kees Cook
2023-05-31 7:57 ` Alexander Potapenko [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='CAG_fn=VOsPw=EqN=P3zPfDyD=ZKYtzUVZ=y42HcqrY2hznx6Ug@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).