From: js1304@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
Wengang Wang <wen.gang.wang@oracle.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: [PATCH 00/18] introduce a new tool, valid access checker
Date: Tue, 28 Nov 2017 16:48:35 +0900 [thread overview]
Message-ID: <1511855333-3570-1-git-send-email-iamjoonsoo.kim@lge.com> (raw)
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Hello,
This patchset introduces a new tool, valid access checker.
Vchecker is a dynamic memory error detector. It provides a new debug feature
that can find out an un-intended access to valid area. Valid area here means
the memory which is allocated and allowed to be accessed by memory owner and
un-intended access means the read/write that is initiated by non-owner.
Usual problem of this class is memory overwritten.
Most of debug feature focused on finding out un-intended access to
in-valid area, for example, out-of-bound access and use-after-free, and,
there are many good tools for it. But, as far as I know, there is no good tool
to find out un-intended access to valid area. This kind of problem is really
hard to solve so this tool would be very useful.
This tool doesn't automatically catch a problem. Manual runtime configuration
to specify the target object is required.
Note that there was a similar attempt for the debugging overwritten problem
however it requires manual code modifying and recompile.
http://lkml.kernel.org/r/<20171117223043.7277-1-wen.gang.wang@oracle.com>
To get more information about vchecker, please see a documention at
the last patch.
Patchset can also be available at
https://github.com/JoonsooKim/linux/tree/vchecker-master-v1.0-next-20171122
Enjoy it.
Thanks.
Joonsoo Kim (14):
mm/kasan: make some kasan functions global
vchecker: introduce the valid access checker
vchecker: mark/unmark the shadow of the allocated objects
vchecker: prepare per object memory for vchecker
vchecker: store/report callstack of value writer
lib/stackdepot: extend stackdepot API to support per-user stackdepot
vchecker: consistently exclude vchecker's stacktrace
vchecker: fix 'remove' handling on callstack checker
mm/vchecker: support inline KASAN build
mm/vchecker: make callstack depth configurable
mm/vchecker: pass allocation caller address to vchecker hook
mm/vchecker: support allocation caller filter
lib/vchecker_test: introduce a sample for vchecker test
doc: add vchecker document
Namhyung Kim (4):
lib/stackdepot: Add is_new arg to depot_save_stack
vchecker: Add 'callstack' checker
vchecker: Support toggle on/off of callstack check
vchecker: Use __GFP_ATOMIC to save stacktrace
Documentation/dev-tools/vchecker.rst | 200 +++++++
drivers/gpu/drm/drm_mm.c | 4 +-
include/linux/kasan.h | 1 +
include/linux/slab.h | 8 +
include/linux/slab_def.h | 3 +
include/linux/slub_def.h | 3 +
include/linux/stackdepot.h | 10 +-
lib/Kconfig.kasan | 21 +
lib/Makefile | 1 +
lib/stackdepot.c | 126 ++--
lib/vchecker_test.c | 117 ++++
mm/kasan/Makefile | 1 +
mm/kasan/kasan.c | 14 +-
mm/kasan/kasan.h | 3 +
mm/kasan/report.c | 12 +-
mm/kasan/vchecker.c | 1089 ++++++++++++++++++++++++++++++++++
mm/kasan/vchecker.h | 43 ++
mm/page_owner.c | 8 +-
mm/slab.c | 47 +-
mm/slab.h | 14 +-
mm/slab_common.c | 25 +
mm/slub.c | 49 +-
22 files changed, 1730 insertions(+), 69 deletions(-)
create mode 100644 Documentation/dev-tools/vchecker.rst
create mode 100644 lib/vchecker_test.c
create mode 100644 mm/kasan/vchecker.c
create mode 100644 mm/kasan/vchecker.h
--
2.7.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-11-28 7:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 7:48 js1304 [this message]
2017-11-28 7:48 ` [PATCH 01/18] mm/kasan: make some kasan functions global js1304
2017-11-28 7:48 ` [PATCH 02/18] vchecker: introduce the valid access checker js1304
2017-11-28 19:41 ` Andi Kleen
2017-11-29 5:36 ` Joonsoo Kim
2017-12-01 5:08 ` kbuild test robot
2017-12-01 8:01 ` Joonsoo Kim
2017-11-28 7:48 ` [PATCH 03/18] vchecker: mark/unmark the shadow of the allocated objects js1304
2017-11-28 7:48 ` [PATCH 04/18] vchecker: prepare per object memory for vchecker js1304
2017-11-28 7:48 ` [PATCH 05/18] vchecker: store/report callstack of value writer js1304
2017-11-28 7:48 ` [PATCH 06/18] lib/stackdepot: Add is_new arg to depot_save_stack js1304
2017-11-28 7:48 ` [PATCH 07/18] lib/stackdepot: extend stackdepot API to support per-user stackdepot js1304
2017-11-28 7:48 ` [PATCH 08/18] vchecker: Add 'callstack' checker js1304
2017-11-28 7:48 ` [PATCH 09/18] vchecker: Support toggle on/off of callstack check js1304
2017-11-28 7:48 ` [PATCH 10/18] vchecker: Use __GFP_ATOMIC to save stacktrace js1304
2017-11-28 7:48 ` [PATCH 11/18] vchecker: consistently exclude vchecker's stacktrace js1304
2017-11-28 7:48 ` [PATCH 12/18] vchecker: fix 'remove' handling on callstack checker js1304
2017-11-28 7:48 ` [PATCH 13/18] mm/vchecker: support inline KASAN build js1304
2017-11-28 7:48 ` [PATCH 14/18] mm/vchecker: make callstack depth configurable js1304
2017-11-28 7:48 ` [PATCH 15/18] mm/vchecker: pass allocation caller address to vchecker hook js1304
2017-12-01 2:39 ` kbuild test robot
2017-12-01 3:01 ` kbuild test robot
2017-11-28 7:48 ` [PATCH 16/18] mm/vchecker: support allocation caller filter js1304
2017-11-28 7:48 ` [PATCH 17/18] lib/vchecker_test: introduce a sample for vchecker test js1304
2017-11-28 7:48 ` [PATCH 18/18] doc: add vchecker document js1304
2017-11-29 9:27 ` [PATCH 00/18] introduce a new tool, valid access checker Dmitry Vyukov
2017-12-01 7:46 ` Joonsoo Kim
2017-12-22 1:51 ` Joonsoo Kim
2018-01-18 22:39 ` Andrew Morton
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=1511855333-3570-1-git-send-email-iamjoonsoo.kim@lge.com \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=namhyung@kernel.org \
--cc=wen.gang.wang@oracle.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