[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170330153018.d59cab6e3819a6dcf86bc609@linux-foundation.org>
Date: Thu, 30 Mar 2017 15:30:18 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: mark.rutland@....com, peterz@...radead.org,
aryabinin@...tuozzo.com, mingo@...hat.com, will.deacon@....com,
kasan-dev@...glegroups.com, linux-mm@...ck.org, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] x86, kasan: add KASAN checks to atomic operations
On Tue, 14 Mar 2017 20:24:11 +0100 Dmitry Vyukov <dvyukov@...gle.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.
Powered by blists - more mailing lists