From: Alexander Potapenko <glider@google.com>
To: glider@google.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, dave.hansen@linux.intel.com, hpa@zytor.com,
akpm@linux-foundation.org, elver@google.com, dvyukov@google.com,
nathan@kernel.org, ndesaulniers@google.com,
kasan-dev@googlegroups.com, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 1/4] x86: kmsan: Don't rename memintrinsics in uninstrumented files
Date: Fri, 3 Mar 2023 15:16:50 +0100 [thread overview]
Message-ID: <CAG_fn=X45qBJKgaZ4xVN=DHwDTYG7HzUb5kTwf79Rs1aJ-f9mg@mail.gmail.com> (raw)
In-Reply-To: <20230303141433.3422671-1-glider@google.com>
This is the second version of the patch. Sorry for the inconvenience.
next prev parent reply other threads:[~2023-03-03 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 14:14 Alexander Potapenko
2023-03-03 14:14 ` [PATCH 2/4] kmsan: another take at fixing memcpy tests Alexander Potapenko
2023-03-03 14:17 ` Alexander Potapenko
2023-03-03 14:59 ` Marco Elver
2023-03-03 14:14 ` [PATCH 3/4] x86: kmsan: use C versions of memset16/memset32/memset64 Alexander Potapenko
2023-03-03 14:17 ` Alexander Potapenko
2023-03-03 14:14 ` [PATCH 4/4] kmsan: add memsetXX tests Alexander Potapenko
2023-03-03 14:17 ` Alexander Potapenko
2023-03-03 15:00 ` Marco Elver
2023-03-03 14:16 ` Alexander Potapenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-01 14:39 [PATCH 1/4] x86: kmsan: Don't rename memintrinsics in uninstrumented files Alexander Potapenko
2023-03-02 11:13 ` Marco Elver
2023-03-02 14:27 ` Alexander Potapenko
2023-03-02 15:13 ` Marco Elver
2023-03-02 15:17 ` Alexander Potapenko
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=X45qBJKgaZ4xVN=DHwDTYG7HzUb5kTwf79Rs1aJ-f9mg@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=tglx@linutronix.de \
--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