From: Alexander Potapenko <glider@google.com>
To: akpm@linux-foundation.org, glider@google.com
Cc: elver@google.com, andreyknvl@google.com, dvyukov@google.com,
mingo@redhat.com, pmladek@suse.com, rostedt@goodmis.org,
sergey.senozhatsky@gmail.com, linux-mm@kvack.org,
linux-api@vger.kernel.org, vbabka@suse.cz,
gregkh@linuxfoundation.org
Subject: [PATCH v3 0/3] Add error_report_end tracepoint to KFENCE and KASAN
Date: Thu, 21 Jan 2021 14:19:12 +0100 [thread overview]
Message-ID: <20210121131915.1331302-1-glider@google.com> (raw)
This patchset adds a tracepoint, error_repor_end, that is to be used by
KFENCE, KASAN, and potentially other bug detection tools, when they
print an error report.
One of the possible use cases is userspace collection of kernel error
reports: interested parties can subscribe to the tracing event via
tracefs, and get notified when an error report occurs.
v3:
- dropped the sysfs interface for log collection
- dropped error_report_start tracepoint
v2:
- added ABI documentation for /sys/kernel/error_report/
- changed error_report_start and error_report end tracepoints to take
a fixed set of values for the error detector
Alexander Potapenko (3):
tracing: add error_report_end trace point
kfence: use error_report_end tracepoint
kasan: use error_report_end tracepoint
include/trace/events/error_report.h | 74 +++++++++++++++++++++++++++++
kernel/trace/Makefile | 1 +
kernel/trace/error_report-traces.c | 12 +++++
mm/kasan/report.c | 8 ++--
mm/kfence/report.c | 2 +
5 files changed, 94 insertions(+), 3 deletions(-)
create mode 100644 include/trace/events/error_report.h
create mode 100644 kernel/trace/error_report-traces.c
--
2.30.0.296.g2bfb1c46d8-goog
next reply other threads:[~2021-01-21 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:19 Alexander Potapenko [this message]
2021-01-21 13:19 ` [PATCH v3 0/3] Add error_report_end tracepoint to KFENCE and KASAN Alexander Potapenko
2021-01-21 13:19 ` [PATCH v3 1/3] tracing: add error_report_end trace point Alexander Potapenko
2021-01-21 13:19 ` Alexander Potapenko
2021-01-21 13:19 ` [PATCH 2/3] kfence: use error_report_end tracepoint Alexander Potapenko
2021-01-21 13:19 ` Alexander Potapenko
2021-01-21 13:19 ` [PATCH 3/3] kasan: " Alexander Potapenko
2021-01-21 13:19 ` Alexander Potapenko
2021-01-22 8:32 ` [PATCH v3 0/3] Add error_report_end tracepoint to KFENCE and KASAN Petr Mladek
2021-01-22 8:41 ` Alexander Potapenko
2021-01-22 8:41 ` Alexander Potapenko
2021-01-22 8:49 ` Petr Mladek
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=20210121131915.1331302-1-glider@google.com \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.