From: "Jörn Engel" <joern@purestorage.com>
To: Alexander Potapenko <glider@google.com>
Cc: Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitriy Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kasan-dev <kasan-dev@googlegroups.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] kfence: show cpu and timestamp in alloc/free info
Date: Tue, 29 Jun 2021 04:40:15 -0700 [thread overview]
Message-ID: <YNsGnyHJL6i1OZFl@cork> (raw)
In-Reply-To: <CAG_fn=V2H7UX8YQYqsQ08D_xF3VKUMCUkafTMVr-ywtki6S0wA@mail.gmail.com>
On Tue, Jun 29, 2021 at 01:34:27PM +0200, Alexander Potapenko wrote:
> On Tue, Jun 29, 2021 at 1:33 PM Marco Elver <elver@google.com> wrote:
> >
> > Record cpu and timestamp on allocations and frees, and show them in
> > reports. Upon an error, this can help correlate earlier messages in the
> > kernel log via allocation and free timestamps.
> >
> > Suggested-by: Joern Engel <joern@purestorage.com>
> > Signed-off-by: Marco Elver <elver@google.com>
>
> Acked-by: Alexander Potapenko <glider@google.com>
Acked-by: Joern Engel <joern@purestorage.com>
Jörn
--
Without a major sea change, nothing that is under copyright today will
ever come out from under it and fall into the public domain.
-- Jake Edge
next prev parent reply other threads:[~2021-06-29 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 11:33 [PATCH] kfence: show cpu and timestamp in alloc/free info Marco Elver
2021-06-29 11:34 ` Alexander Potapenko
2021-06-29 11:40 ` Jörn Engel [this message]
2021-07-13 16:19 ` 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=YNsGnyHJL6i1OZFl@cork \
--to=joern@purestorage.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).