From: Christopher Lameter <cl@linux.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, malchev@google.com
Subject: Re: [PATCH v3] slub: extend slub debug to handle multiple slabs
Date: Fri, 28 Sep 2018 14:20:11 +0000 [thread overview]
Message-ID: <01000166208d1f55-2b13fdf8-a1a5-4a64-80f2-2e1a5314285e-000000@email.amazonses.com> (raw)
In-Reply-To: <20180928111139.27962-1-atomlin@redhat.com>
On Fri, 28 Sep 2018, Aaron Tomlin wrote:
> Extend the slub_debug syntax to "slub_debug=<flags>[,<slub>]*", where <slub>
> may contain an asterisk at the end. For example, the following would poison
> all kmalloc slabs:
Acked-by: Christoph Lameter <cl@linux.com>
prev parent reply other threads:[~2018-09-28 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 11:11 Aaron Tomlin
2018-09-28 14:20 ` Christopher Lameter [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=01000166208d1f55-2b13fdf8-a1a5-4a64-80f2-2e1a5314285e-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malchev@google.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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