From: Petr Mladek <pmladek@suse.com>
To: Alexander Potapenko <glider@google.com>
Cc: akpm@linux-foundation.org, elver@google.com,
andreyknvl@google.com, dvyukov@google.com, mingo@redhat.com,
rostedt@goodmis.org, sergey.senozhatsky@gmail.com,
linux-mm@kvack.org, linux-api@vger.kernel.org, vbabka@suse.cz,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v3 0/3] Add error_report_end tracepoint to KFENCE and KASAN
Date: Fri, 22 Jan 2021 09:32:33 +0100 [thread overview]
Message-ID: <YAqNoTWfp7HQ9c5m@alley> (raw)
In-Reply-To: <20210121131915.1331302-1-glider@google.com>
On Thu 2021-01-21 14:19:12, Alexander Potapenko wrote:
> 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
Just for record. This approach looks reasonable to me.
Thanks for removing the sysfs interface. It would have been
a potential can of worms.
I do not feel eligible to add any tag. I am neither familiar
with the tracepoint nor the KFENCE or KASAN code.
Best Regards,
Petr
next prev parent reply other threads:[~2021-01-22 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` [PATCH 2/3] kfence: use error_report_end tracepoint Alexander Potapenko
2021-01-21 13:19 ` [PATCH 3/3] kasan: " Alexander Potapenko
2021-01-22 8:32 ` Petr Mladek [this message]
2021-01-22 8:41 ` [PATCH v3 0/3] Add error_report_end tracepoint to KFENCE and KASAN 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=YAqNoTWfp7HQ9c5m@alley \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).