From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: mark.rutland@arm.com, peterz@infradead.org,
aryabinin@virtuozzo.com, mingo@redhat.com, will.deacon@arm.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86, kasan: add KASAN checks to atomic operations
Date: Thu, 30 Mar 2017 15:30:18 -0700 [thread overview]
Message-ID: <20170330153018.d59cab6e3819a6dcf86bc609@linux-foundation.org> (raw)
In-Reply-To: <cover.1489519233.git.dvyukov@google.com>
On Tue, 14 Mar 2017 20:24:11 +0100 Dmitry Vyukov <dvyukov@google.com> wrote:
> KASAN uses compiler instrumentation to intercept all memory accesses.
> But it does not see memory accesses done in assembly code.
> One notable user of assembly code is atomic operations. Frequently,
> for example, an atomic reference decrement is the last access to an
> object and a good candidate for a racy use-after-free.
I'm getting a pile of build errors from this patchset (and related
patches). Due to messed up merge fixing, probably. Please the review
process has been a bit bumpy.
So I'll drop
kasan-allow-kasan_check_read-write-to-accept-pointers-to-volatiles.patch
asm-generic-x86-wrap-atomic-operations.patch
asm-generic-x86-wrap-atomic-operations-fix.patch
asm-generic-add-kasan-instrumentation-to-atomic-operations.patch
asm-generic-fix-compilation-failure-in-cmpxchg_double.patch
x86-remove-unused-atomic_inc_short.patch
x86-asm-generic-add-kasan-instrumentation-to-bitops.patch
for now. Please resend (against -mm or linux-next) when the dust has
settled.
prev parent reply other threads:[~2017-03-30 22:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 19:24 [PATCH 0/3] x86, kasan: add KASAN checks to atomic operations Dmitry Vyukov
2017-03-14 19:24 ` [PATCH 1/3] kasan: allow kasan_check_read/write() to accept pointers to volatiles Dmitry Vyukov
2017-03-14 19:24 ` [PATCH 2/3] asm-generic, x86: wrap atomic operations Dmitry Vyukov
2017-03-20 16:41 ` Andrey Ryabinin
2017-03-20 17:17 ` Mark Rutland
2017-03-21 9:25 ` Andrey Ryabinin
2017-03-21 10:41 ` Mark Rutland
2017-03-21 18:06 ` Dmitry Vyukov
2017-03-21 21:20 ` Arnd Bergmann
2017-03-22 10:42 ` Dmitry Vyukov
2017-03-22 11:30 ` Arnd Bergmann
2017-03-22 12:14 ` Dmitry Vyukov
2017-03-22 12:48 ` Arnd Bergmann
2017-03-24 6:52 ` Ingo Molnar
2017-03-24 7:14 ` Dmitry Vyukov
2017-03-24 8:39 ` Dmitry Vyukov
2017-03-24 10:57 ` Ingo Molnar
2017-03-24 12:46 ` Dmitry Vyukov
2017-03-28 7:52 ` Ingo Molnar
2017-03-28 9:27 ` Peter Zijlstra
2017-03-28 9:46 ` Dmitry Vyukov
2017-03-28 9:51 ` Ingo Molnar
2017-03-28 9:56 ` Dmitry Vyukov
2017-03-28 10:15 ` Ingo Molnar
2017-03-28 16:29 ` Dmitry Vyukov
2017-03-14 19:24 ` [PATCH 3/3] asm-generic: add KASAN instrumentation to " Dmitry Vyukov
2017-03-30 22:30 ` Andrew Morton [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=20170330153018.d59cab6e3819a6dcf86bc609@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).