From: David Gow <davidgow@google.com>
To: trishalfonso@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,
David Gow <davidgow@google.com>
Subject: [PATCH v6 1/5] Add KUnit Struct to Current Task
Date: Fri, 17 Apr 2020 20:18:29 -0700 [thread overview]
Message-ID: <20200418031833.234942-2-davidgow@google.com> (raw)
In-Reply-To: <20200418031833.234942-1-davidgow@google.com>
From: Patricia Alfonso <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>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: David Gow <davidgow@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 4418f5cb8324..e50c568a8dc7 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1188,6 +1188,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.1.301.g55bc3eb7cb9-goog
next prev parent reply other threads:[~2020-04-18 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 3:18 [PATCH v6 0/5] KUnit-KASAN Integration David Gow
2020-04-18 3:18 ` David Gow [this message]
2020-04-18 3:18 ` [PATCH v6 2/5] KUnit: KASAN Integration David Gow
2020-04-20 5:43 ` Walter-ZH Wu (吳祖寰)
2020-04-18 3:18 ` [PATCH v6 3/5] KASAN: Port KASAN Tests to KUnit David Gow
2020-04-21 15:38 ` Andrey Konovalov
2020-04-18 3:18 ` [PATCH v6 4/5] KASAN: Testing Documentation David Gow
2020-04-21 15:37 ` Andrey Konovalov
2020-04-18 3:18 ` [PATCH v6 5/5] mm: kasan: Do not panic if both panic_on_warn and kasan_multishot set David Gow
2020-04-21 15:39 ` Andrey Konovalov
2020-04-18 15:28 ` [PATCH v6 0/5] KUnit-KASAN Integration Alan Maguire
2020-04-24 6:36 ` David Gow
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=20200418031833.234942-2-davidgow@google.com \
--to=davidgow@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=brendanhiggins@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=trishalfonso@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.