From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>,
Christoph Lameter <cl@linux.com>,
Linux Memory Management List <linux-mm@kvack.org>,
David Rientjes <rientjes@google.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: slab/for-next: 102 Tests: 102 Passed, 0 Failed
Date: Sat, 26 Aug 2023 11:03:53 +0900 [thread overview]
Message-ID: <CAB=+i9QEo0yzAUHYv8r15KLJRp_da_7ZvwgvzpaC9-89=98Ejw@mail.gmail.com> (raw)
Hi, this is the test result of slab/for-next testing,
targeting the testing of various SLUB configurations.
# Test Result
slab/for-next: 102 Tests: 102 Passed, 0 Failed
git repository:https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git/
git branch: for-next
git commit: 66489e5487b7 ("Merge branch 'slab/for-6.6/random_kmalloc'
into slab/for-next")
This is Hyeonggon's project aimed at helping to reduce kernel bugs
during the development stage. Feel free to share any opinions; I will
make adjustments accordingly next time.
# Additional Information
At the moment the test case is only a boot test.
The configuration matrix is as follows:
# Note: SLAB is not tested
PREEMPT=PREEMPT_NONE,PREEMPT_VOLUNTARY,PREEMPT
DEBUG=e,d # enables KASAN, lockdep, DEBUG_VM*
SLUB_HARDENING=e,d # enables SLUB_FREELIST_*
SLUB_DEBUG_ON=e,d
SLAB_MERGE_DEFAULT=e,d
SLUB_TINY=e,d
SLUB_CPU_PARTIAL=e,d
and the combination filter is:
!((SLUB_TINY == "e") && (SLAB_MERGE_DEFAULT == "d" || SLUB_CPU_PARTIAL
== "e" || SLUB_HARDENING == "e" || SLUB_DEBUG_ON == "e"))
reply other threads:[~2023-08-26 2:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAB=+i9QEo0yzAUHYv8r15KLJRp_da_7ZvwgvzpaC9-89=98Ejw@mail.gmail.com' \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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