From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Benjamin Berg <benjamin@sipsolutions.net>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>,
"Shuah Khan" <shuah@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Nicolas Schier" <nicolas.schier@linux.dev>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, workflows@vger.kernel.org,
"Kees Cook" <kees@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 12/15] kunit: Introduce UAPI testing framework
Date: Fri, 27 Jun 2025 10:27:36 +0200 [thread overview]
Message-ID: <20250627100608-9eff2270-8f5b-49d4-9fe3-54a12a14dd25@linutronix.de> (raw)
In-Reply-To: <8cfa715301c7c357c5d6c82fabd9b53d2fa01182.camel@sipsolutions.net>
On Fri, Jun 27, 2025 at 08:58:11AM +0200, Benjamin Berg wrote:
> On Fri, 2025-06-27 at 06:20 +0200, Thomas Weißschuh wrote:
> > On Thu, Jun 26, 2025 at 08:11:17PM +0200, Benjamin Berg wrote:
> > > I ran into two minor issues trying out the patches, see inline.
> >
> > Thanks for testing the series.
> >
> > > On Thu, 2025-06-26 at 08:10 +0200, Thomas Weißschuh wrote:
> > > > Enable running UAPI tests as part of kunit.
> > > > The selftests are embedded into the kernel image and their output is
> > > > forwarded to kunit for unified reporting.
> > > >
> > > > The implementation reuses parts of usermode drivers and usermode
> > > > helpers. However these frameworks are not used directly as they make it
> > > > impossible to retrieve a thread's exit code.
> > > >
> > > > Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> > > >
> > > > [SNIP]
> > > > +/**
> > > > + * KUNIT_UAPI_EMBED_BLOB() - Embed another build artifact into the kernel
> > > > + * @_name: The name of symbol under which the artifact is embedded.
> > > > + * @_path: Path to the artifact on disk.
> > > > + *
> > > > + * Embeds a build artifact like a userspace executable into the kernel or current module.
> > > > + * The build artifact is read from disk and needs to be already built.
> > > > + */
> > > > +#define KUNIT_UAPI_EMBED_BLOB(_name, _path) \
> > > > + asm ( \
> > > > + " .pushsection .rodata, \"a\" \n" \
> > > > + " .global " __stringify(CONCATENATE(_name, _data)) " \n" \
> > > > + __stringify(CONCATENATE(_name, _data)) ": \n" \
> > > > + " .incbin " __stringify(_path) " \n" \
> > > > + " .size " __stringify(CONCATENATE(_name, _data)) ", " \
> > > > + ". - " __stringify(CONCATENATE(_name, _data)) " \n" \
> > > > + " .global " __stringify(CONCATENATE(_name, _end)) " \n" \
> > > > + __stringify(CONCATENATE(_name, _end)) ": \n" \
> > > > + " .popsection \n" \
> > > > + ); \
> > > > + \
> > > > + extern const char CONCATENATE(_name, _data)[]; \
> > > > + extern const char CONCATENATE(_name, _end)[]; \
> > > > + \
> > > > + static const struct kunit_uapi_blob _name = { \
> > > > + .path = _path, \
> > > > + .data = CONCATENATE(_name, _data), \
> > > > + .end = CONCATENATE(_name, _end), \
> > > > + } \
> > >
> > > For me, the compiler could not find the files for the ".incbin" unless
> > > I added an include path. i.e. adding
> > > ccflags-y := -I$(obj)
> > > to lib/kunit/Makefile fixed the problem for me.
> >
> > Can you share some more details on your build setup?
> > This worked for me as-is and also passed 0day build testing.
>
> Funny, I ran this on a Fedora 41 with gcc --version saying
> gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
>
> I tried both 32 and 64 bit builds for ARCH=um.
>
> Attaching my current kernel configuration and the last few lines of a
> V=1 build.
>
> The kernel I used is a bit newer than what you had. Applied on top of
> ee88bddf7f2f5d1f1da87dd7bedc734048b70e88 (bpf-fixes merge).
So this happens because you are building inside the source tree.
scripts/Makefile.lib has this block:
# $(src) for including checkin headers from generated source files
# $(obj) for including generated headers from checkin source files
ifdef building_out_of_srctree
_c_flags += $(addprefix -I, $(src) $(obj))
_a_flags += $(addprefix -I, $(src) $(obj))
_cpp_flags += $(addprefix -I, $(src) $(obj))
endif
Apparently GNU/clang assemblers don't look for .incbin/.include files next to
the including files [0].
In contrast, the ARM compiler does (at least according to its docs) [1].
Maybe we can work around this in the macro, but I assume this will become even
uglier. So for the next revision I'll use your proposal of explicit cflags.
Or if Masahiro prefers to have a more global and generic solution, we can do that.
[0] https://sourceware.org/binutils/docs/as/I.html
[1] https://developer.arm.com/documentation/dui0801/l/Directives-Reference/INCBIN
Thomas
next prev parent reply other threads:[~2025-06-27 8:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 6:10 [PATCH v4 00/15] " Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 01/15] kbuild: userprogs: avoid duplication of flags inherited from kernel Thomas Weißschuh
2025-07-03 13:59 ` Nicolas Schier
2025-07-04 21:51 ` Masahiro Yamada
2025-06-26 6:10 ` [PATCH v4 02/15] kbuild: userprogs: also inherit byte order and ABI " Thomas Weißschuh
2025-07-03 14:00 ` Nicolas Schier
2025-07-04 21:51 ` Masahiro Yamada
2025-06-26 6:10 ` [PATCH v4 03/15] kbuild: doc: add label for userprogs section Thomas Weißschuh
2025-07-03 14:00 ` Nicolas Schier
2025-07-04 21:55 ` Masahiro Yamada
2025-06-26 6:10 ` [PATCH v4 04/15] init: re-add CONFIG_CC_CAN_LINK_STATIC Thomas Weißschuh
2025-07-03 14:00 ` Nicolas Schier
2025-07-04 21:55 ` Masahiro Yamada
2025-06-26 6:10 ` [PATCH v4 05/15] init: add nolibc build support Thomas Weißschuh
2025-07-03 14:01 ` Nicolas Schier
2025-06-26 6:10 ` [PATCH v4 06/15] fs,fork,exit: export symbols necessary for KUnit UAPI support Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 07/15] kunit: tool: Add test for nested test result reporting Thomas Weißschuh
2025-07-01 21:26 ` Rae Moar
2025-06-26 6:10 ` [PATCH v4 08/15] kunit: tool: Don't overwrite test status based on subtest counts Thomas Weißschuh
2025-07-01 21:11 ` Rae Moar
2025-07-03 15:29 ` Thomas Weißschuh
2025-07-04 12:55 ` Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 09/15] kunit: tool: Parse skipped tests from kselftest.h Thomas Weißschuh
2025-07-01 21:22 ` Rae Moar
2025-07-03 15:59 ` Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 10/15] kunit: Always descend into kunit directory during build Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 11/15] kunit: qemu_configs: loongarch: Enable LSX/LSAX Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 12/15] kunit: Introduce UAPI testing framework Thomas Weißschuh
2025-06-26 18:11 ` Benjamin Berg
2025-06-27 4:20 ` Thomas Weißschuh
2025-06-27 6:58 ` Benjamin Berg
2025-06-27 8:27 ` Thomas Weißschuh [this message]
2025-06-26 6:10 ` [PATCH v4 13/15] kunit: uapi: Add example for UAPI tests Thomas Weißschuh
2025-06-26 6:10 ` [PATCH v4 14/15] kunit: uapi: Introduce preinit executable Thomas Weißschuh
2025-07-12 9:49 ` Muhammad Usama Anjum
2025-06-26 6:10 ` [PATCH v4 15/15] kunit: uapi: Validate usability of /proc Thomas Weißschuh
2025-07-07 18:18 ` [PATCH v4 00/15] kunit: Introduce UAPI testing framework Jonathan Corbet
2025-07-08 5:51 ` Thomas Weißschuh
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=20250627100608-9eff2270-8f5b-49d4-9fe3-54a12a14dd25@linutronix.de \
--to=thomas.weissschuh@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=benjamin@sipsolutions.net \
--cc=brauner@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=rmoar@google.com \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=w@1wt.eu \
--cc=workflows@vger.kernel.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