From: David Rientjes <rientjes@google.com>
To: Oliver Glitta <glittao@gmail.com>
Cc: cl@linux.com, penberg@kernel.org, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, vbabka@suse.cz, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/2] slub: remove resiliency_test() function
Date: Wed, 17 Mar 2021 11:54:34 -0700 (PDT) [thread overview]
Message-ID: <398a728-dc1c-5089-5578-7af596d616ac@google.com> (raw)
In-Reply-To: <20210316124118.6874-2-glittao@gmail.com>
On Tue, 16 Mar 2021, glittao@gmail.com wrote:
> From: Oliver Glitta <glittao@gmail.com>
>
> Function resiliency_test() is hidden behind #ifdef
> SLUB_RESILIENCY_TEST that is not part of Kconfig, so nobody
> runs it.
>
> This function is replaced with kselftest for SLUB added
> by the previous patch "selftests: add a kselftest for SLUB
> debugging functionality".
>
> Signed-off-by: Oliver Glitta <glittao@gmail.com>
Very nice!
Acked-by: David Rientjes <rientjes@google.com>
next prev parent reply other threads:[~2021-03-17 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 12:41 [PATCH 1/2] selftests: add a kselftest for SLUB debugging functionality glittao
2021-03-16 12:41 ` [PATCH 2/2] slub: remove resiliency_test() function glittao
2021-03-17 11:25 ` Vlastimil Babka
2021-03-17 18:54 ` David Rientjes [this message]
2021-03-17 8:36 ` [selftests] e48d82b67a: BUG_TestSlub_RZ_alloc(Not_tainted):Redzone_overwritten kernel test robot
2021-03-17 11:29 ` Vlastimil Babka
2021-03-17 18:53 ` David Rientjes
2021-03-23 0:02 ` Vlastimil Babka
2021-03-22 5:41 ` Oliver Sang
2021-03-17 11:24 ` [PATCH 1/2] selftests: add a kselftest for SLUB debugging functionality Vlastimil Babka
2021-03-17 18:54 ` David Rientjes
2021-03-18 11:47 ` Marco Elver
2021-03-19 10:46 ` Vlastimil Babka
2021-03-19 11: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=398a728-dc1c-5089-5578-7af596d616ac@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=glittao@gmail.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=shuah@kernel.org \
--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