From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Andy Shevchenko" <andy@kernel.org>,
"David Gow" <davidgow@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Brendan Higgins" <brendanhiggins@google.com>,
"Rae Moar" <rmoar@google.com>, "Kees Cook" <kees@kernel.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Yury Norov" <yury.norov@gmail.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Naveen N . Rao" <naveen.n.rao@linux.ibm.com>,
"Anil S Keshavamurthy" <anil.s.keshavamurthy@intel.com>,
"David S . Miller" <davem@davemloft.net>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mark Brown" <broonie@kernel.org>,
linux-hardening@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Simon Horman" <horms@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Daniel Latypov" <dlatypov@google.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"David Howells" <dhowells@redhat.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Marco Elver" <elver@google.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Nathan Chancellor" <nathan@kernel.org>,
"Fangrui Song" <maskray@google.com>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: Re: [PATCH 3/6] lib: Move KUnit tests into tests/ subdirectory
Date: Fri, 11 Oct 2024 18:29:49 +0200 [thread overview]
Message-ID: <600a11af-cf42-45d9-9be8-b7066d90c89f@csgroup.eu> (raw)
In-Reply-To: <CAHp75Vecwe_LaSKSprwfrdpDhoJbXgajQUVY23L+VyGoxtGH7A@mail.gmail.com>
Le 11/10/2024 à 17:21, Andy Shevchenko a écrit :
> [Vous ne recevez pas souvent de courriers de andy.shevchenko@gmail.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>
> On Fri, Oct 11, 2024 at 5:20 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> On Fri, Oct 11, 2024 at 3:57 PM Andy Shevchenko <andy@kernel.org> wrote:
>>> On Fri, Oct 11, 2024 at 03:38:00PM +0200, Geert Uytterhoeven wrote:
>>>> On Fri, Oct 11, 2024 at 12:44 PM Andy Shevchenko <andy@kernel.org> wrote:
>>>>> On Fri, Oct 11, 2024 at 03:25:07PM +0800, David Gow wrote:
>
> ...
>
>>>>>> rename lib/{ => tests}/bitfield_kunit.c (100%)
>>>>>> rename lib/{ => tests}/checksum_kunit.c (100%)
>>>>>> rename lib/{ => tests}/cmdline_kunit.c (100%)
>>>>>> rename lib/{ => tests}/cpumask_kunit.c (100%)
>>>>>> rename lib/{ => tests}/fortify_kunit.c (100%)
>>>>>> rename lib/{ => tests}/hashtable_test.c (100%)
>>>>>> rename lib/{ => tests}/is_signed_type_kunit.c (100%)
>>>>>> rename lib/{ => tests}/kunit_iov_iter.c (100%)
>>>>>> rename lib/{ => tests}/list-test.c (100%)
>>>>>> rename lib/{ => tests}/memcpy_kunit.c (100%)
>>>>>> rename lib/{ => tests}/overflow_kunit.c (100%)
>>>>>> rename lib/{ => tests}/siphash_kunit.c (100%)
>>>>>> rename lib/{ => tests}/slub_kunit.c (100%)
>>>>>> rename lib/{ => tests}/stackinit_kunit.c (100%)
>>>>>> rename lib/{ => tests}/string_helpers_kunit.c (100%)
>>>>>> rename lib/{ => tests}/string_kunit.c (100%)
>>>>>> rename lib/{ => tests}/test_bits.c (100%)
>>>>>> rename lib/{ => tests}/test_fprobe.c (100%)
>>>>>> rename lib/{ => tests}/test_hash.c (100%)
>>>>>> rename lib/{ => tests}/test_kprobes.c (100%)
>>>>>> rename lib/{ => tests}/test_linear_ranges.c (100%)
>>>>>> rename lib/{ => tests}/test_list_sort.c (100%)
>>>>>> rename lib/{ => tests}/test_sort.c (100%)
>>>>>> rename lib/{ => tests}/usercopy_kunit.c (100%)
>>>>>
>>>>> While I support the idea, I think this adds an additional churn in creating a
>>>>> duplicate 'test' in the filenames. Why they all can't be cut while removing?
>>>>> (at least this question is not answered in the commit message)
>>>>
>>>> To avoid duplicate *.ko file names?
>>>
>>> With what? Sorry, but I don't see how it's a problem. These are test cases.
>>> Do they use kernel command line parameters? If so, shouldn't KUnit take care
>>> about it in a more proper way?
>>
>> If .e.g. lib/list_sort.o could be modular, its module would be called
>> "list_sort.ko", conflicting with the "list_sort.ko" test module.
But as it is now in lib/tests/, the module will also be installed in
tests/ subdir, so it shouldn't clash anymore ?
You'd have:
/lib/modules/lib/list_sort.ko and
/lib/modules/lib/tests/list_sort.ko
Or did I miss something ?
>
> Can't this be solved by automatically adding a prefix in Makefile for
> kunit tests, for example?
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2024-10-11 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011072509.3068328-2-davidgow@google.com>
2024-10-11 7:25 ` [PATCH 3/6] lib: Move KUnit tests into tests/ subdirectory David Gow
2024-10-11 9:17 ` Vlastimil Babka
2024-10-11 10:44 ` Andy Shevchenko
2024-10-11 13:38 ` Geert Uytterhoeven
2024-10-11 13:57 ` Andy Shevchenko
2024-10-11 14:14 ` Geert Uytterhoeven
2024-10-11 15:21 ` Andy Shevchenko
2024-10-11 16:29 ` Christophe Leroy [this message]
2024-10-11 17:22 ` Andy Shevchenko
2024-10-11 17:20 ` Kees Cook
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=600a11af-cf42-45d9-9be8-b7066d90c89f@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arnd@arndb.de \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=charlie@rivosinc.com \
--cc=davem@davemloft.net \
--cc=davidgow@google.com \
--cc=dhowells@redhat.com \
--cc=dlatypov@google.com \
--cc=elver@google.com \
--cc=geert@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=maskray@google.com \
--cc=mhiramat@kernel.org \
--cc=mic@digikod.net \
--cc=nathan@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=palmer@rivosinc.com \
--cc=rmoar@google.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
--cc=vbabka@suse.cz \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).