From: Patricia Alfonso <trishalfonso@google.com>
To: davidgow@google.com, brendanhiggins@google.com,
aryabinin@virtuozzo.com, dvyukov@google.com, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
Patricia Alfonso <trishalfonso@google.com>
Subject: [PATCH v3 1/4] Add KUnit Struct to Current Task
Date: Wed, 1 Apr 2020 11:09:06 -0700 [thread overview]
Message-ID: <20200401180907.202604-4-trishalfonso@google.com> (raw)
In-Reply-To: <20200401180907.202604-1-trishalfonso@google.com>
In order to integrate debugging tools like KASAN into the KUnit
framework, add KUnit struct to the current task to keep track of the
current KUnit test.
Signed-off-by: Patricia Alfonso <trishalfonso@google.com>
---
include/linux/sched.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 04278493bf15..7ca3e5068316 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1180,6 +1180,10 @@ struct task_struct {
unsigned int kasan_depth;
#endif
+#if IS_ENABLED(CONFIG_KUNIT)
+ struct kunit *kunit_test;
+#endif
+
#ifdef CONFIG_FUNCTION_GRAPH_TRACER
/* Index of current stored address in ret_stack: */
int curr_ret_stack;
--
2.26.0.rc2.310.g2932bb562d-goog
next prev parent reply other threads:[~2020-04-01 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 18:09 [PATCH v3 0/4] KUnit-KASAN Integration Patricia Alfonso
2020-04-01 18:09 ` [PATCH v3 2/4] KUnit: KASAN Integration Patricia Alfonso
2020-04-02 10:23 ` Dmitry Vyukov
2020-04-02 15:54 ` Andrey Konovalov
2020-04-02 16:37 ` Patricia Alfonso
2020-04-02 16:40 ` Andrey Konovalov
2020-04-01 18:09 ` [PATCH v3 4/4] KASAN: Testing Documentation Patricia Alfonso
2020-04-02 10:34 ` Dmitry Vyukov
2020-04-01 18:09 ` Patricia Alfonso [this message]
2020-04-01 18:09 ` [PATCH v3 3/4] KASAN: Port KASAN Tests to KUnit Patricia Alfonso
2020-04-02 10:32 ` Dmitry Vyukov
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=20200401180907.202604-4-trishalfonso@google.com \
--to=trishalfonso@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=juri.lelli@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox