Commit cb88577b authored by David Gow's avatar David Gow Committed by Shuah Khan

Fix linked-list KUnit test when run multiple times

A few of the lists used in the linked-list KUnit tests (the
for_each_entry{,_reverse} tests) are declared 'static', and so are
not-reinitialised if the test runs multiple times. This was not a
problem when KUnit tests were run once on startup, but when tests are
able to be run manually (e.g. from debugfs[1]), this is no longer the
case.

Making these lists no longer 'static' causes the lists to be
reinitialised, and the test passes each time it is run. While there may
be some value in testing that initialising static lists works, the
for_each_entry_* tests are unlikely to be the right place for it.
Signed-off-by: default avatarDavid Gow <davidgow@google.com>
Reviewed-by: default avatarBrendan Higgins <brendanhiggins@google.com>
Signed-off-by: default avatarShuah Khan <skhan@linuxfoundation.org>
parent 97752c39
...@@ -659,7 +659,7 @@ static void list_test_list_for_each_prev_safe(struct kunit *test) ...@@ -659,7 +659,7 @@ static void list_test_list_for_each_prev_safe(struct kunit *test)
static void list_test_list_for_each_entry(struct kunit *test) static void list_test_list_for_each_entry(struct kunit *test)
{ {
struct list_test_struct entries[5], *cur; struct list_test_struct entries[5], *cur;
static LIST_HEAD(list); LIST_HEAD(list);
int i = 0; int i = 0;
for (i = 0; i < 5; ++i) { for (i = 0; i < 5; ++i) {
...@@ -680,7 +680,7 @@ static void list_test_list_for_each_entry(struct kunit *test) ...@@ -680,7 +680,7 @@ static void list_test_list_for_each_entry(struct kunit *test)
static void list_test_list_for_each_entry_reverse(struct kunit *test) static void list_test_list_for_each_entry_reverse(struct kunit *test)
{ {
struct list_test_struct entries[5], *cur; struct list_test_struct entries[5], *cur;
static LIST_HEAD(list); LIST_HEAD(list);
int i = 0; int i = 0;
for (i = 0; i < 5; ++i) { for (i = 0; i < 5; ++i) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment