All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Alexander Potapenko" <glider@google.com>,
	"Jörn Engel" <joern@purestorage.com>,
	"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, 13 Jul 2021 18:19:32 +0200	[thread overview]
Message-ID: <CANpmjNOif53i2zx5hZCN97U9Hb_BPv15dchSTfg9qpJa8iZ3rA@mail.gmail.com> (raw)
In-Reply-To: <YNsGnyHJL6i1OZFl@cork>

Hello, Andrew,

This patch is ready to be picked up.

Many thanks,
-- Marco

On Tue, 29 Jun 2021 at 13:40, 'Jörn Engel' via kasan-dev
<kasan-dev@googlegroups.com> wrote:
> 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>

      reply	other threads:[~2021-07-13 16:19 UTC|newest]

Thread overview: 6+ 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:33 ` Marco Elver
2021-06-29 11:34 ` Alexander Potapenko
2021-06-29 11:34   ` Alexander Potapenko
2021-06-29 11:40   ` Jörn Engel
2021-07-13 16:19     ` Marco Elver [this message]

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=CANpmjNOif53i2zx5hZCN97U9Hb_BPv15dchSTfg9qpJa8iZ3rA@mail.gmail.com \
    --to=elver@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=joern@purestorage.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 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.