[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191011140536.03c3e25500b31ddcfa0f542b@linux-foundation.org>
Date: Fri, 11 Oct 2019 14:05:36 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Gow <davidgow@...gle.com>
Cc: shuah@...nel.org, brendanhiggins@...gle.com, keescook@...omium.org,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH linux-kselftest/test v2] lib/list-test: add a test for
the 'list' doubly linked list
On Thu, 10 Oct 2019 11:56:31 -0700 David Gow <davidgow@...gle.com> wrote:
> Add a KUnit test for the kernel doubly linked list implementation in
> include/linux/list.h
>
> Each test case (list_test_x) is focused on testing the behaviour of the
> list function/macro 'x'. None of the tests pass invalid lists to these
> macros, and so should behave identically with DEBUG_LIST enabled and
> disabled.
>
> Note that, at present, it only tests the list_ types (not the
> singly-linked hlist_), and does not yet test all of the
> list_for_each_entry* macros (and some related things like
> list_prepare_entry).
<looks at kunit>
Given that everything runs at late_initcall time, shouldn't everything
be __init, __initdata etc so all the code and data doesn't hang around
for ever?
Powered by blists - more mailing lists