Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon,  9 Aug 2021 13:25:08 +0200
Message-Id: <20210809112516.682816-1-elver@google.com>
Mime-Version: 1.0
Subject: [PATCH 0/8] kcsan: Cleanups and fix reporting for scoped accesses
From:   Marco Elver <elver@google.com>
To:     elver@google.com, paulmck@kernel.org
Cc:     mark.rutland@arm.com, dvyukov@google.com, glider@google.com,
        boqun.feng@gmail.com, kasan-dev@googlegroups.com,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

This series contains several test fixes and cleanups, as well as fixing
reporting for scoped accesses.

Thus far, scoped accesses' stack traces could point anywhere in the
scope, and can be quite confusing when searching for the relevant access
scope several stack frames down. This is fixed by using the original
instruction pointer of the location where the scoped access was set up.

There are more changes coming that depend on the fixed reporting, but it
made more sense to detach the changes in this series as they are useful
on their own and only touch core KCSAN code.

Marco Elver (8):
  kcsan: test: Defer kcsan_test_init() after kunit initialization
  kcsan: test: Use kunit_skip() to skip tests
  kcsan: test: Fix flaky test case
  kcsan: Add ability to pass instruction pointer of access to reporting
  kcsan: Save instruction pointer for scoped accesses
  kcsan: Start stack trace with explicit location if provided
  kcsan: Support reporting scoped read-write access type
  kcsan: Move ctx to start of argument list

 include/linux/kcsan-checks.h |  3 ++
 kernel/kcsan/core.c          | 75 ++++++++++++++++++++---------------
 kernel/kcsan/kcsan.h         |  8 ++--
 kernel/kcsan/kcsan_test.c    | 62 +++++++++++++++++++----------
 kernel/kcsan/report.c        | 77 ++++++++++++++++++++++++++++++------
 5 files changed, 156 insertions(+), 69 deletions(-)

-- 
2.32.0.605.g8dce9f2422-goog