From: Marco Elver <elver@google.com>
To: peterz@infradead.org, aryabinin@virtuozzo.com,
dvyukov@google.com, glider@google.com, andreyknvl@google.com,
mark.rutland@arm.com, hpa@zytor.com
Cc: corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, arnd@arndb.de, jpoimboe@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, kasan-dev@googlegroups.com,
Marco Elver <elver@google.com>
Subject: [PATCH v5 0/3] Bitops instrumentation for KASAN
Date: Thu, 13 Jun 2019 14:59:47 +0200 [thread overview]
Message-ID: <20190613125950.197667-1-elver@google.com> (raw)
Previous version:
http://lkml.kernel.org/r/20190613123028.179447-1-elver@google.com
* Only changed lib/test_kasan in this version.
Marco Elver (3):
lib/test_kasan: Add bitops tests
x86: Use static_cpu_has in uaccess region to avoid instrumentation
asm-generic, x86: Add bitops instrumentation for KASAN
Documentation/core-api/kernel-api.rst | 2 +-
arch/x86/ia32/ia32_signal.c | 2 +-
arch/x86/include/asm/bitops.h | 189 ++++------------
arch/x86/kernel/signal.c | 2 +-
include/asm-generic/bitops-instrumented.h | 263 ++++++++++++++++++++++
lib/test_kasan.c | 81 ++++++-
6 files changed, 382 insertions(+), 157 deletions(-)
create mode 100644 include/asm-generic/bitops-instrumented.h
--
2.22.0.rc2.383.gf4fbbf30c2-goog
next reply other threads:[~2019-06-13 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 12:59 Marco Elver [this message]
2019-06-13 12:59 ` [PATCH v5 0/3] Bitops instrumentation for KASAN Marco Elver
2019-06-13 12:59 ` [PATCH v5 1/3] lib/test_kasan: Add bitops tests Marco Elver
2019-06-13 12:59 ` Marco Elver
2019-06-13 12:59 ` [PATCH v5 2/3] x86: Use static_cpu_has in uaccess region to avoid instrumentation Marco Elver
2019-06-13 12:59 ` Marco Elver
2019-06-13 12:59 ` [PATCH v5 3/3] asm-generic, x86: Add bitops instrumentation for KASAN Marco Elver
2019-06-13 12:59 ` Marco Elver
2019-06-17 14:00 ` [PATCH v5 0/3] Bitops " Marco Elver
2019-06-17 14:00 ` Marco Elver
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=20190613125950.197667-1-elver@google.com \
--to=elver@google.com \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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