From: Uriel Guajardo <urielguajardojr@gmail.com>
To: brendanhiggins@google.com, catalin.marinas@arm.com,
akpm@linux-foundtation.org
Cc: changbin.du@intel.com, rdunlap@infradead.org,
masahiroy@kernel.org, 0x7f454c46@gmail.com,
urielguajardo@google.com, krzk@kernel.org,
kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, linux-mm@kvack.org
Subject: [PATCH 0/2] KUnit-Kmemleak Integration
Date: Mon, 6 Jul 2020 21:03:25 +0000 [thread overview]
Message-ID: <20200706210327.3313498-1-urielguajardojr@gmail.com> (raw)
From: Uriel Guajardo <urielguajardo@google.com>
With these patches, KUnit can access and manually run kmemleak in every test
case. Any errors caught by kmemleak will cause the KUnit test to fail.
This patchset relies on "kunit: KASAN integration", which places the
currently running kunit test in task_struct. [1]
[1] https://lore.kernel.org/linux-kselftest/20200606040349.246780-2-davidgow@google.com
Uriel Guajardo (2):
kunit: support kunit failures from debugging tools
kunit: kmemleak integration
include/kunit/test-bug.h | 15 +++++++++++++
include/kunit/test.h | 1 +
include/linux/kmemleak.h | 11 ++++++++++
lib/Kconfig.debug | 26 +++++++++++++++++++++++
lib/kunit/test.c | 46 +++++++++++++++++++++++++++++++++++-----
mm/kmemleak.c | 27 +++++++++++++++++------
6 files changed, 115 insertions(+), 11 deletions(-)
create mode 100644 include/kunit/test-bug.h
--
2.27.0.212.ge8ba1cc988-goog
next reply other threads:[~2020-07-06 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 21:03 Uriel Guajardo [this message]
2020-07-06 21:03 ` [PATCH 1/2] kunit: support kunit failures from debugging tools Uriel Guajardo
2020-07-06 21:03 ` [PATCH 2/2] kunit: kmemleak integration Uriel Guajardo
2020-07-06 21:13 [PATCH 0/2] KUnit-Kmemleak Integration Uriel Guajardo
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=20200706210327.3313498-1-urielguajardojr@gmail.com \
--to=urielguajardojr@gmail.com \
--cc=0x7f454c46@gmail.com \
--cc=akpm@linux-foundtation.org \
--cc=brendanhiggins@google.com \
--cc=catalin.marinas@arm.com \
--cc=changbin.du@intel.com \
--cc=kernel@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.org \
--cc=urielguajardo@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